yashsingh1/xdaforums huggingface dataset:
[Windows Mobile Software Development] RoryB:
I meant in my registry I have three folders under "\\Documents and Settings\\", and you seem to have replaced them with a single call of "\\Documents and Settings\\".

This does make more sense than the three separate calls.

I also see "\\mxip_swmgmt.vol" as an added file.

If I cook this in my Wizard, what will the average user notice if anything?
[Windows Mobile Software Development] !Aman!:
speed and a snappier device ;)
[Windows Mobile Software Development] dsixda:
While I find this thread very useful, any reason why the following tag is found at the bottom of the page? -- "dsixda a loser" :( ;( Ameet?
[Windows Mobile Software Development] Ameet:
Tried playing with the dllfirst value and chaged to the last dll in dump_MemoryMaps + 1 but didnt work so well. Stuck at first boot screen, which means there's something more to it

Can some kind soul guide us here on how to find out the reference to value of physfirst in the imgfs VM? If I can get to know that I may be able to know the limit to which I can push it to get more free RAM space
[Windows Mobile Software Development] DupinBJK:
What would you need, exactly, to know the offset at which physfirst can be found (in that case xip.bin), or to know where else it is referenced in the rom ?
[Windows Mobile Software Development] Ameet:
Post 73 is more detailed question. The extract where I am stuck without any info is

The physfirst is concerned, I have no idea where to look for the stuff that is there between the below values and till what limit I can pull up the 80000000 value and push down the 83000000 (End of RAM) value to make more space for free RAM area

03ffa000 - 04000000 L00006000 Virtual base address of busenum.dll
[B][COLOR=red]04000000 - 80000000 [/COLOR][/B]L7c000000 NUL
80000000 - 80000000 L00000000 Start: first physical address

Looks like we have to get into more cleaning once this gets sorted :rolleyes:
[Windows Mobile Software Development] DupinBJK:
We're tricycling in a barrel of melassa, AB, I can tell you where to get them (see post #83), but not to what extent they can be modified (not yet :rolleyes:)
[Windows Mobile Software Development] pfcsabre:
A little help here :)

I'm in the stage where the INSERT is insert.exe -i xip_out.bin -o OS.nb.payload -d 0x00320000 -s 0x004C0000 but since I'm cooking for Touch Pro:

- how to get the starting offset of imgfs?

- is the starting offset of xip in Touch Pro also 0x00320000? (I noticed this address from extracting xip.bin by RomMaster method, so I'm assuming it's this)

thanks in advance!
[Windows Mobile Software Development] try:
Can somebody help me.

I got something like:

80000000 - 80000000 L00000000 Start: first physical address
80000000 - 80001000 L00001000 RomLDR.PARTHDR
80001000 - 8007d598 L0007c598 o32 region_0 rva=00001000 vsize=0007c598 real=80001000 psize=0007c598 f=60000020 for nk.exe
80077fb4 - 8007d598 L000055e4 !!!!!!!!!!!!!!!!!!
80077fb4 - 80077ff5 L00000041 o32 region_1 rva=00002000 vsize=00000041 real=00012000 psize=00000044 f=c8000040 for device.exe
80077ff5 - 80078ecc L00000ed7 NUL
80078ecc - 80078fa0 L000000d4 o32 region_1 rva=00004000 vsize=000000d4 real=01ff8000 psize=000000d4 f=c0000040 for diskcache.dll
80078fa0 - 80078ff8 L00000058 o32 region_3 rva=00006000 vsize=00001000 real=00000000 psize=00000058 f=42000042 for diskcache.dll
80078ff8 - 80079000 L00000008 NUL
80079000 - 80080814 L00007814 o32 region_0 rva=00001000 vsize=00007814 real=03ff0000 psize=00007814 f=60000020 for cachefilt.dll
8007e000 - 80080814 L00002814 !!!!!!!!!!!!!!!!!!
8007e000 - 80081230 L00003230 o32 region_3 rva=0007e000 vsize=00003230 real=8007e000 psize=00003230 f=40000040 for nk.exe
80080e14 - 80081230 L0000041c !!!!!!!!!!!!!!!!!!
80080e14 - 80080f74 L00000160 o32 region_1 rva=00009000 vsize=00000160 real=01ffe000 psize=00000160 f=c0000040 for cachefilt.dll

What should I do to get rid of the !!!!!!!!!!!!!!!!!! ?

Attached is my MAP.TXT file for complete reference.

TIA,
[Windows Mobile Software Development] cruzzmz:
example:

80080e14-1230= new value nk.exe

have to do from bottom going upwards

as for me i usually use xip addr tool ... but then maybe it wont work on certain devices

regards
[Windows Mobile Software Development] try:
Thank you for your help cruzzmz.

If I am not mistaken, someone mentioned that we need m'reloc_nk for relocating nk.exe Am I right?

Also from your comment above, I want to confirm with the MAP.TXT i have. Just to make sure I donot do something wrong.

You said as example:

80080e14-1230= new value nk.exe

from my MAP.TXT

8007e000 - 80081230 L00003230 o32 region_3 rva=0007e000 vsize=0000[COLOR=Blue]3230[/COLOR] real=8007e000 psize=00003230 f=40000040 for nk.exe
80080e14 - 80081230 L0000041c !!!!!!!!!!!!!!!!!!
80080e14 - 80080f74 L00000160 o32 region_1 rva=00009000 vsize=00000160 real=01ffe000 psize=00000160 f=c0000040 for cachefilt.dll

Might be what you mean is:

80080e14-3230= new value nk.exe

I need your confirmation.

TIA,
[Windows Mobile Software Development] Ameet:
My Friend, the first post of this thread is your answer here :)

:( Looks like we have to wait for someone who actually knows to translate the 4xxxxxxx - 8xxxxxxxx space and tell us what happens in there and to what extent we can modify or push the limits of 803xxxxx values to gain more free ram :(
[Windows Mobile Software Development] cruzzmz:
nope pretty sure that my explanation earlier is correct u can always refer to the 1st post since it is quite easy to understand (Thanks to AB)

MReloc_nk is use when u want to relocate ur free ram ... see my previous posts on the Q & A

that is correct right AB?
[Windows Mobile Software Development] Ameet:
Right. He needs to realloc the address of region 0 or 1 depending on the device which can be determined from map.txt at the last of the file which is the ram space
[Windows Mobile Software Development] Ameet:
Looks like you might have a case of improper porting. Can you post your traced steps of what you did right from the start? We may be able to help you in this then. I'm saying this since you are not showing any signs of overlaps in the vbase or realaddr values but in the copyentries (if thats what these are known as) Yet the ram doesnt show overlaps either. So posting your steps here would mean helpful out here
[Windows Mobile Software Development] cruzzmz:
the master has spoken .... ;)

BTW what is copyentries??

also i want to confirm something, using MReloc_nk could u change the value using hex values? since mine wont let me ehmmm .... :confused:
[Windows Mobile Software Development] Ameet:
Dont know much about copyentries yet but you can surely expect to see a guide on those too in here soon ;) Have never used hex editing on nk since I dont understand much of hexing. So I use only the Mreloc_nk to realloc nk values. But it works for me like a charm :D
[Windows Mobile Software Development] cruzzmz:
AB what i mean here is not hex as in hacking the nk.exe but hex value as in 123456789abcdef .. when i use mreloc_nk, i cant enter ie: 8000c123
[Windows Mobile Software Development] evalu8t0r:
For every complex problem there is a solution thats simple neat and wrong, this was one of them :o)

...now I'm wondering if anyone knows how M'reloc.exe finds o32_realaddr and o32_vsize (under 'o32 total') I've been looking at imageinfo.bin which seems to be the only file M'reloc opens and I can't figure out how it finds the values

Looking at imageinfo.txt didnt help me either
[Windows Mobile Software Development] Ameet:
Aah!! That I remember :D What I do normally is copy 8000c12 and paste it in the text box and then add the final number by hand and then doit ;)
[Windows Mobile Software Development] Ameet:
I forgive you this time for posting the same question in both my threads. Avoid it in future coz it creates confusion in the readers for what to follow. Removing your post as of now since I have already replied in my other guide thread
[Windows Mobile Software Development] :
I keep getting an error while trying to do NBmerge. Unexpected erroor, would you like to send report.

nbmerge.exe -kaiser os.nb
executing nbmerge.exe with data chunk size = 0x800 and extra chunk size = 0x8 on file os.nb

Parition 0: start sector 0x00000002, total 0x0000063e
first used 0x00000002, used 0x0000063e
Partion 1: start sector: 0x00000640, total 0x00000800
first used 0x00000640, used 0x0000061d

but then if i use

nbmerge.exe -kaiser os.nb -conservative
executing nbmerge.exe with data chunk size = 0x800 and extra chunk size = 0x8 on file os.nb
checking os.nb for bad NAND block marker
-----------> Found BAD BLOCK marker! <------------
Do Not Flash This File!
sector:0x1
all extra bytes:
0x004d
0x0053
0x0046
0x004c
0x0053
0x0048
0x0035
0x0030

then it works but the file is bad. and idea about what i am doing wrong?
[Windows Mobile Software Development] Ameet:
I dont think its anyway related to XIP porting so no idea from me except for the fact that nbmerge is used to merge the payload into nb :) (atleast for now) Maybe Dupin or Cruzz may help you out
[Windows Mobile Software Development] Ameet:
I really dont know buddy.. But I'll try and find out who put it up.. Unfortunately the tagging is open for all users
[Windows Mobile Software Development] CRACING:
Yes sometimes and no sometimes. In this thread, the tick box is disabled which cannot be removed and also in some other threads.
[Windows Mobile Software Development] Ameet:
I know.. I saw when I disabled that tag right now.. I frankly dont know who did this, but I do apologise for that stupid action by whoever.. Tried to look it up in mod tools but couldnt find anything :(
[Windows Mobile Software Development] dsixda:
Thanks!

Keep up the good work Ameet, and congrats on marriage!

For my own XIP porting, I have found that the XIP extracting tool that came with Platform Rebuilder has made it all easier -- it has worked about 99% of the time (if you search the thread, someone has posted a link to the tutorial). The other times I had to use the XIP porting GUI (write maps, make packages, etc.)
[Windows Mobile Software Development] Ameet:
Thanks brother :) Not got a chance to look into new ways of porting yet :D But will soon catch up again :D
[Windows Mobile Software Development] poifgh:
"Click “make pkgs” to get “OEMXipKernel” and “MSXipKernel” folders inside \Files and \Modules"

I am using TPC kitchen and make pkgs doesnt yield MSXipKernel or OEM folders.. Any help?
[Windows Mobile Software Development] utak3r:
well, it depends on what this kitchen produces inside the folder... provide us some listing :)
[Windows Mobile Software Development] Nik Ahmad:
The purpose of high file system index (pro & contra)

Hi ameet :D

I am newbie cooker, What is the purpose of high file system index? and what is disadvantages if we adjust parameter as per recommended by Mr Aman? Tqvm :confused:
[Windows Mobile Software Development] jianwei87:
i just write the new_xip.bin file to OS.NB.payload when i trying to do the next step it wont work why?

The next step i would like to do is nbmerge.exe –kaiser OS.nb

the device im going to port is xperia. so which step or cmd i type/do wrongly?
[Windows Mobile Software Development] RoryB:
I have cooked this in and things do seem to be quicker. I have not clocked anything as before or after, but when I flash a ROM I have a file that I open in word to get my email signature to copy and it seems that file opens a lot faster.
[Windows Mobile Software Development] qjsmartphone:
I have an Idea well since you are a porting expert I wonder if we can start a team to create a special device normally alone we don't have money but I have an idea for creating a super phone where we can make money for our work I will give you more details later
[Windows Mobile Software Development] afeng11:
M'Reloc_nk can reloc nk.exe,but how to reloc other modules in the ram section?thanks

808b3000 - 808b3000 L00000000 Start: start of RAM

808b3000 - 808b8000 L00005000 NUL

808b8000 - 808bc000 L00004000 initialized data of region_1 stratad.dll

808bc000 - 808bd000 L00001000 initialized data of region_1 rootbus.dll

808bd000 - 808be000 L00001000 initialized data of region_1 buses.dll

808be000 - 808bf000 L00001000 initialized data of region_1 giisr.dll

808bf000 - 808c0000 L00001000 initialized data of region_1 nvbsp.dll

808c0000 - 808ca000 L0000a000 uninitialized data of region_2 nk.exe

808ca000 - 808f0000 L00026000 initialized data of region_3 nk.exe

808f0000 - 80908000 L00018000 initialized data of region_1 trueffs.dll

80908000 - 80909000 L00001000 initialized data of region_3 nvbsp.dll

80909000 - 8090a000 L00001000 initialized data of region_1 bsp_serial.dll

8090a000 - 8090b000 L00001000 initialized data of region_1 bsp_usbfn.dll

8090b000 - 8090c000 L00001000 initialized data of region_1 battdrvr.dll

8090c000 - 8090d000 L00001000 initialized data of region_1 bsp_keypadbacklight.dll

8090d000 - 8090e000 L00001000 initialized data of region_1 serialusbfn.dll

8090e000 - 8090f000 L00001000 initialized data of region_1 irsir.dll

8090f000 - 80910000 L00001000 initialized data of region_2 nvbacklight.dll

80910000 - 80917000 L00007000 initialized data of region_1 rilgsm.dll

80917000 - 80918000 L00001000 initialized data of region_2 NVSDHC.dll

80918000 - 80919000 L00001000 initialized data of region_1 usbmsc.dll

80919000 - 8091a000 L00001000 initialized data of region_1 sdhc_hx.dll

8091a000 - 8091b000 L00001000 initialized data of region_1 atadisk.dll

8091b000 - 8091c000 L00001000 initialized data of region_1 otg.dll

8091c000 - 8091d000 L00001000 initialized data of region_1 spkphone.dll

8091d000 - 80922000 L00005000 initialized data of region_2 nvcam.dll

80922000 - 80923000 L00001000 initialized data of region_1 usbd.dll

80923000 - 80924000 L00001000 initialized data of region_2 nvrm.dll

80924000 - 80935000 L00011000 initialized data of region_2 nvddi.dll

80935000 - 80936000 L00001000 initialized data of region_1 ohci2.dll

80936000 - 80937000 L00001000 initialized data of region_1 tvout.dll

80937000 - 80938000 L00001000 initialized data of region_1 bsp_wavedev.dll

80938000 - 80939000 L00001000 initialized data of region_1 bsp_pwrbutton.dll

80939000 - 8093a000 L00001000 initialized data of region_1 sdmemory.dll

8093a000 - 8093b000 L00001000 initialized data of region_1 nleddrvr.dll

8093b000 - 8093c000 L00001000 initialized data of region_1 serial.dll

8093c000 - 8093d000 L00001000 initialized data of region_1 sdbus.dll

8093d000 - 8093e000 L00001000 initialized data of region_1 bsp_cpupwr.dll

8093e000 - 8093f000 L00001000 initialized data of region_1 usbdisk6.dll

8093f000 - 80940000 L00001000 initialized data of region_1 btagext.dll

80940000 - 80940000 L00000000 ------ start of RAM free space

80940000 - 84000000 L036c0000 NUL

84000000 - 84000000 L00000000 End: end of RAM
[Windows Mobile Software Development] oldsap:
hi, i was following THIS POST but my phone wont boot up. This is what i did:

xip.bin <= i used a ported xip using xipkitchen (this xip.bin works)

i then used xipport to dump xip.bin to an OUT folder, and also made maps for the map.txt

my original MAP.txt content is like this

80319000 - 80319000 L00000000 Start: start of RAM
80319000 - 80320000 L00007000 NUL
80320000 - 80326000 L00006000 uninitialized data of region_1 nk.exe
80326000 - 8038b000 L00065000 initialized data of region_2 nk.exe
8038b000 - 8039e000 L00013000 NUL
8039e000 - 8039e000 L00000000 ------ start of RAM free space
8039e000 - 83abe000 L03720000 NUL
83abe000 - 83abe000 L00000000 End: end of RAM

then after following the link above, i had this

80319000 - 80319000 L00000000 Start: start of RAM
80319000 - 8031f000 L00006000 uninitialized data of region_1 nk.exe
8031f000 - 80384000 L00065000 initialized data of region_2 nk.exe
80384000 - 80384000 L00000000 ------ start of RAM free space
80384000 - 83abe000 L0373a000 NUL
83abe000 - 83abe000 L00000000 End: end of RAM

i also edited the imageinfo.tx inside my \OUT\Modules\nk.exe folder to this:

o32[1].o32_vsize: 00006000
o32[1].o32_rva: 0006E000
o32[1].o32_psize: 00000000
o32[1].o32_dataptr: 00000000
o32[1].o32_realaddr: [B][COLOR="Red"]R=80319000[/COLOR][/B]
o32[1].o32_flags: C0000080

o32[2].o32_vsize: 00024A0C
o32[2].o32_rva: 00074000
o32[2].o32_psize: 00000A00
o32[2].o32_dataptr: P+00074208
o32[2].o32_realaddr: [B][COLOR="Red"]R=8031f000[/COLOR][/B]
o32[2].o32_flags: C0000040

and my ROMHDR.txt to this

ulRAMStart: R=80319000
ulRAMFree: [B][COLOR="Red"]80384000[/COLOR][/B]
ulRAMEnd: 83ABE000

any other thing i have to do or did not do?
[Windows Mobile Software Development] afeng11:
your nk.exe region_1 address must 10000 scale of start of RAM at least,so it maybe a value such as 80320000、80330000,and region_2 of nk.exe must be 80326000 or 80336000,you can adjust nk.exe with xipport,then your ppc can boot.
[Windows Mobile Software Development] oldsap:
oh, so it should start at 80320000 NOT 80319000?

so what do i do with the lost 7000? do i NUL it like this?

80319000 - 80319000 L00000000 Start: start of RAM
80319000 - 80320000 L00007000 NUL
80320000 - 80326000 L00006000 uninitialized data of region_1 nk.exe

then it will be the same as the untouched xip :)

[COLOR="Red"]80319000 - 80319000 L00000000 Start: start of RAM
80319000 - 80320000 L00007000 NUL
80320000 - 80326000 L00006000 uninitialized data of region_1 nk.exe[/COLOR]
80326000 - 8038b000 L00065000 initialized data of region_2 nk.exe
8038b000 - 8039e000 L00013000 NUL
8039e000 - 8039e000 L00000000 ------ start of RAM free space
8039e000 - 83abe000 L03720000 NUL
83abe000 - 83abe000 L00000000 End: end of RAM

but the sample HERE was almost like the one i had

80306000 - 80306000 L00000000 Start: start of RAM
[COLOR="Red"]80306000 - 8030c000 L00006000 uninitialized data of region_1 nk.exe[/COLOR]
8030c000 - 80331000 L00025000 initialized data of region_2 nk.exe
80331000 - 80331000 L00000000 ------ start of RAM free space
80331000 - 83400000 L030cf000 NUL
83400000 - 83400000 L00000000 End: end of RAM
[Windows Mobile Software Development] afeng11:
some devices has these requests as above
[Windows Mobile Software Development] oldsap:
sorry for being a noob on this, but what does that mean?
[Windows Mobile Software Development] utak3r:
it means that for some devices you can't reloc nk so it doesn't leave any empty spaces... and your example shows it. So you have to round those addresses and fill the rest with NUL.
[Windows Mobile Software Development] oldsap:
oh, too bad for my device :(
[Windows Mobile Software Development] At0mAng:
Might be a dumb question...

So if I have native kernel 6.5 kernel from 21839 build and port it over to 23XXX build is my kernel still native to my device?
[Windows Mobile Software Development] utak3r:
if you won't overwrite it... then yes, of course :cool:
[Windows Mobile Software Development] oldsap:
may i ask how this is done on IDA Pro please? i opened the nk.exe using IDA Pro but i get a different view. i tried to search "string": aL2dsize0xX but it can't find it.
[Windows Mobile Software Development] utak3r:
OK guys, I wrote a little tutorial on how to load modules (especially nk.exe) into IDA Pro:

http://utak3r.buzzdev.org/2009/08/30/loading-modules-into-ida-pro/

Have a nice reading! :)
[Windows Mobile Software Development] pak1to:
thanks man for detailed summary
[Windows Mobile Software Development] oldsap:
thank you very very much for spending some time on this sir. it's much appreciated.
[Windows Mobile Software Development] oldsap:
when i get to step 4 of the tutorial, and i click on OK, it says WARNING: the loading address should belong to RAM or ROM then it doesn't get past that step.
[Windows Mobile Software Development] utak3r:
you've calculated your values wrong...
[Windows Mobile Software Development] oldsap:
got it. i subtracted the value instead of adding. maybe because of too much excitement in trying this out :D sorry :)
[Windows Mobile Software Development] bgcngm:
I've been trying for a while to port a XIP for my device (ETEN/ACER DX900), but I was never able to build a working XIP using buildxip v0.54. I don't get any error, but the phone simply doesn't boot. I think it has something to do with nk.exe module relocation (I have seen some users talking about this here).

Here (please rename from .txt to .7z) you can find the MAP files created with XIPPort from my device's xip.bin (the original) and from the rebuilt xip.bin (using buildxip v0.54, but without touching any file/module).

Can anyone explain me what am I doing wrong? The only way I'm able to port a XIP is to use XIPKitchen beta 6. :(
[Windows Mobile Software Development] afeng11:
O2 XDA Flame ROM put all OEMDrivers into xip section,so it is very difficult to port xip.anyone can tell me how to convert xip modules to imgfs modules?thank advance!!
[Windows Mobile Software Development] slimli:
I'm trying to cook rom by new kitchen PRB by Bepe. But my xip.bin don't include Boot.rgu. I've try to conert boot.hv to boot.rgu and put it to Xip.bin, but I have no idea how to do that

My phone is Apache
[Windows Mobile Software Development] slimli:
Great Thx:D:D:D:D:D:D:D
[Windows Mobile Software Development] utak3r:
set _FLATRELEASEDIR=.\some_directory
rgucomp.exe -nologo -o some_directory\boot.hv >some_directory\boot.rgu
[Windows Mobile Software Development] slimli:
Thanks but I'm sure I've done the right thing converting hv-rgu but it won't boot
[Windows Mobile Software Development] utak3r:
so it seems it's another problem... does your screen change its brightness during boot?
[Windows Mobile Software Development] bgcngm:
Does anyone knows how to use buildxip in way that nk.exe isn't relocated? Maybe someone know how to use the advanced options:
[Windows Mobile Software Development] XRAY MAN:
hi every one

utak3r :D

can I do the porting of XIP auto :D ??

thanks alot
[Windows Mobile Software Development] utak3r:
Sorry man, but I don't understand your question ;)

If we're taling about porting XIP section, then it depends on a device: for newer HTC devices you can use automatic methods, they will work for you.
[Windows Mobile Software Development] XRAY MAN:
Yes, these my question my device is HD but what the automatic method for that ??

thanks alot :D
[Windows Mobile Software Development] utak3r:
Have you tried already ervius' kitchen?
[Windows Mobile Software Development] md_bluelily:
Hi,

Is there any guide to teach how to XIP port WM6.5 source for Wizard ?

I tried the usual porting taught here, but my device stuck at the 2nd screen.

I searched a lot and found out that this is because of bad XIP. I was not able to find the right procedure to do this.

Thanks.

Best Regards.
[Windows Mobile Software Development] XRAY MAN:
Yes,but only for cook without port the XIP & SYS only add/remove packages and tweks :D
[Windows Mobile Software Development] utak3r:
So, it's now a good moment for taking another step :)

Remember: in ROM folder you have MSXIPKernel, which you get from a new XIP to be ported and OEMXIPKernel, which is yours device files.

Try it... if you run into problems, ask.
[Windows Mobile Software Development] md_bluelily:
I'm still searching, asking, trying and testing with no success.

Please if you know how or if you know some source for it, tell me.

Thanks.
[Windows Mobile Software Development] XRAY MAN:
Thanks alot bro :o

I will try that now :D