yashsingh1/xdaforums huggingface dataset:
[Windows Mobile] Pank789:
hi

i am beginner in rom development i used ur kitchen to build the rom for htcp3400 (old) but device stuck at boot screen itself.

also what if we change something in sys folder what is its impact?

also is xip porting necessary only when u want to port rom from one device to other ..?

is there any tutorial which can provide a guide on steps to consider to increase the ram memory which cooking ROM..?

thanks in advance.. :)
[Windows Mobile] ervius:
ok, give me your nk.exe from trinity, (in file and module format!) and I'll try to fix it, if possible....

bye!
[Windows Mobile] ervius:
yes, and I'm thinking also about a same visualkitchen, but in old style, with no platformrebuilder use.....

but time to time! ;)
[Windows Mobile] mike1986.:
ervius I have a strenge problem since 9.1

I was building a ROM and just for a try I disabled SDKcert. Now I want to build ROM with SDKcert but even if I enable SKDcert it doesn't work. Some registry tweaks which were working before doesn't work now also...
[Windows Mobile] bobsbbq:
Is it capable now or in the future?

I tried the following but none of them worked.

OEM\Blackstone\Lite\0409

OEM\Blackstone\Lite\COMMON

OEM\Blackstone\Premium\0409

OEM\Blackstone\Premium\COMMON

EXT\Blackstone\COMMON\Lite\Blackstone_External_Packages\

EXT\Blackstone\COMMON\Premium\Blackstone_External_Packages\

Can you give me a correct example if it will work?
[Windows Mobile] mike1986.:
I think I have found the answer for my qestion. I tried yesterday to cook with real 6.5 aku which doesn't work. Then I flashed my Diamond with correct ROM but is it possible, that checking and cooking once the rom with real wm6.5 aku changed nk.exe file? And now I hava to restore it?

EDIT:

No, it doesn't help. I don't know what to do :(
[Windows Mobile] mac_es:
Here you have as module, how can I obtain as file?

If I use recmod I obtain:

Error! ProcessCase0: bit 5 is zero!

Thank you very much
[Windows Mobile] ervius:
give me intere xip.bin, I'll extract the files from it
[Windows Mobile] ervius:
why do you need lite and premium when you can load and save all kind of roms you want for your device!?!?
[Windows Mobile] NRGZ28:
Just sent you some more coffee money erv.. Don't stop making this kitchen better :)
[Windows Mobile] mahjsa:
C++ Error

I was just trying to build a rom but after update to ver9.3 I get packagerebuilder error. (Just after reading in all files)

Note: I removed all dsm files because I didn't think there was a use for them in this kitchen. Could this be the problem?
[Windows Mobile] hilaireg:
@ervius:

Where did u hide your PayPal Donation link?

* EDIT *

Nevermind; staring at me in the Kitchen ... LOL

Cheers,
[Windows Mobile] ervius:
thanks for doantions.....

at 1st post new_kitchen beta, I didn't try yet, but it builds WOM in old style, with wmreloc ecc....

for now only imgfs is builded, if device boots, I'm try to insert code also to build (xipporterex) xip at runtime with proper build ;)

try it and report!!!

bye!

P.S.: you have to reinsert ".VM" module into sys\build\shared\common\ folder...

bye!
[Windows Mobile] bobsbbq:
OK I guess I'm having a memory fart or something. Could you or someone else please explain to me how to do multiple builds? Ok I know I can put all the different packages in EXT but that gets to be a long list and a little confusing with the naming of packages. For Example my lite build uses 90% different packages than the premium. The names look similar without the Blackstone, or Topaz in the name etc.

For the OEM the OperatorPkg is drastically different between Lite and Premium so I do see how I can have 2 identical names in the same folder? Same with OEMVersion.

Thanks,

EDIT: I found a way but it seems the Kitchen will only recognize numbers, not letters. So Here is what I have done. If someone knows a bettere way let me know.

OEM\BlackStone\0409-1

OEM\BlackStone\0409-2 [I moved the OemVersion to the 0409 so it can be edited and used for each build]

OEM\BlackStone\0409-3

OEM\BlackStone\Common

EXT\BlackStone\21232-1\BlackStone_External_Packages

EXT\BlackStone\21232-2\BlackStone_External_Packages

EXT\BlackStone\21232-3\BlackStone_External_Packages

EXT\BlackStone\Common

I now have 3 different build platforms. I can use the load and save ROM to build these different version. Would it be a problem to add letters in the EXT and OEM input fields.
[Windows Mobile] bobsbbq:
I have noticed one other problem since my switch to the new kitchen. When I reply to a message in Opera the font characters are all messed up? It doesn't happen in IE. Any ideas on this? See Screen shot
[Windows Mobile] mac_es:
Ok, Here you have

Thanks again...
[Windows Mobile] NRGZ28:
May I ask why you're going this direction ? We have your old kitchen to that if we want :)
[Windows Mobile] ervius:
becouse a lot of users wants share theyr works, but is only an idea, maybe roms don't boot.....(you can ever choice if new or old style ;) )

are only my experiments, and all of you could tell me if work ;)

P.S.: thanks a lot for new donators!!!!

I tryed, rom doesn't boot.... :(

ok, we'll stay only on platformrebuilder ;)
[Windows Mobile] ervius:
find in s000 nk.exe module the hex values:

8324A0E3013083E3

and change to:

8424A0E3013083E3

after flash, if rom boots, you' ll have some mega RAM memory more ;)

bye!
[Windows Mobile] mac_es:
Thanks, I will try asap and I'wll post the results
[Windows Mobile] B4PJS:
Ervius: In your first post you mentioned a "protected mode checkbox" but I cant find it. Where abouts is this? Sorry if this is a dumb question.

B
[Windows Mobile] ervius:
old try, the rom can be dump, but doesn't start, so ever protected ;)
[Windows Mobile] B4PJS:
Cool, thought it was just me being an idiot!!

Cheers for all your work mate :)

BTW can you post your package tool as I lost my copy when i upgraded my computer/kitchens recently.
[Windows Mobile] mac_es:
It doesn't boot :(

Thanks anyway

Whith both nk.exe (modified and not modified) PRB reports this:

RAM IMAGE: 0x80000000 - 0x80262c48

RAM: 0x80263000 - 0x8029c000 - Used for kernel modules

0x8029c000 - 0x83a00000 - 55 MB free
[Windows Mobile] B4PJS:
Hey Ervius, I have noticed a minor bug (?) in that when you make changes to packages but dont save the ROM, it processes the ROM from the saved file rather than from the selected items in the list.
[Windows Mobile] anryl:
beta1

module with file overwrite error

executing raws2nbh.bat error

created ruu_ ok size 69mb

NON BOOTING ROM yet :cool:
[Windows Mobile] mahjsa:
Stupid question?

Just like yesterday I receive a MS visual C++ error (from platformrebuilder?)

All directories are processed up to the last EXT package. Then I get this weird error.

This is the message:

Runtime Error!

Program: path\platformrebuilder.exe

This application has requested the Runtime to terminate it in an unusual way.

Please contact the application's support team for more information.

My question: do i need to keep all dsm-files in the proper directories? I thought that a new dsm would be made at compiling the ROM. So I removed all dsm-files. Is this the cause of the error or could there be another cause?

Thanks for help.
[Windows Mobile] anryl:
overwriting more modules with modules kitchen error

put ext/files all modules from oemdrivers again it will crash :eek:
[Windows Mobile] ervius:
not allways,

is allways a problem for paltformrebuilder.exe when a file overwrite a module, becouse platformrebuilder (a bug???) try to cut the module, but find a file instead, so, flag on visualkitchen "warn on overwrite", and you can see all modules(IN UPPERCASE) and relative files (in lowercase) or modules (IN UPPERCASE!) that overwrite original one, only have to select the preferred file and with right mouse click, overwrite the original module with preferred file, and retry to build rom ;)

bye!
[Windows Mobile] anryl:
for the new oldkitchenbuild how do u create xip.bin
[Windows Mobile] mahjsa:
So somewhere in the kitchen I am working on there are double files/modules. Thanks very much for the help.

I tried with the "warn on overwrite" flag but didn't get a warning. Does this mean I have to look for doubles in files/modules manually?

BTW Until now not much progress in building a working ROM. Hope that plattformrebuilder will be compatible with my A701. I will let you know when I succeed in building a working ROM with this kitchen for the A701.
[Windows Mobile] ervius:
not possible for now, and for me rom doesn't boot.....
[Windows Mobile] mike1986.:
What should I do to put optimized XIP into kitchen? HTC Diamond WM6.5 21232. Do I have to use some tools or just replace files?
[Windows Mobile] mac_es:
Hi ervius,

Now that I'm confortable whith the nes kitchen I remembered that I was using the "old" implantxip from bepe. I have tried yours and the rom doesn't boot (it doesn't show the first splash).

The same xip/packages/kitchen but whith bepe's implantxip boots correctly.

I attach my payload (imgfs reduced, whith urlrd removed and xip size adjusted) and the xip.bin if you have time to look at it... if not it doesn't matter as whith bepe's one is working

I have compared the resulting payload after implanting the xip and they look quite different...

Thanks
[Windows Mobile] Ameet:
Hi Ervius

I need you to guide me and others on this

http://xdaforums.com/showpost.php?p=3805736&postcount=1015

I know I am cross posting, hopefully Noonski wont ban me for it :D but this if is successful for Diamond nk.exe then it will be one of the greatest tutorials ever written :D:cool:
[Windows Mobile] ervius:
All done ;)

bye!
[Windows Mobile] ervius:
strange, implaintxip (mine ot bepe's) only write xip.bin into payload at certain address, address is stored into MBR, so also mine writes xip.bin into right offset, if have problem with mine, use bepe's one..... ;)
[Windows Mobile] mac_es:
The addresses that show your implantxip are correct, the same that show bepe's one, the same that show xipporteex. Ok I will use bepe's one whithout problem.

cheers
[Windows Mobile] ervius:
yes, but for some roms (smartphones) bepe's one give some errors, mine works well, but, my implantix.exe was little bugged (only for some payload that are cleaned completelly from ULDR Section.....), solved and inserted in tools\ folder of visualkitchen version 9.4 at first post (solved also some other bugs on "import packages" function! ;) )

bye!!!
[Windows Mobile] ervius:
version 9.4 refixed for implantxip.exe (IMGFS Start section wrong for some other payload!) Solved!
[Windows Mobile] mac_es:
Something "strange" i see:

This is whith bepe's one:

IMPLANTXIP Copyright (c) 2007-2008 bepe @ xda-devs Jun 7 2008 11:44:57

XIP section at offset: 0x00020000
IMG section at offset: [COLOR="Red"]0x002A0000
[/COLOR]
Done!
Obtaining IMGFS...
ImgfsFromNb 2.1rc2

Sector size is 0x200 bytes
ImgFs partition starts at 0x002a0000 and ends at 0x002c0000
Dumping IMGFS at offset 0x002a0000 (size 0x00020000)

Whith yours:

Implantxip by ervius!!! (Fixed!)

ROM Block is: 00000200

XIP Start at: 00020000
[COLOR="Red"]XIP size is : 002FFFFF
XIP Ends at : 0031FFFF
IMG Start at: 00320000[/COLOR]

XIP Inserted into: OS.nb.payload
Obtaining IMGFS...
ImgfsFromNb 2.1rc2

Sector size is 0x200 bytes
ImgFs partition starts at[COLOR="Red"] 0x002a0000 [/COLOR]and ends at 0x002c0000
Dumping IMGFS at offset 0x002a0000 (size 0x00020000)

whith yours (not fixed)

Implantxipx by ervius!!!

ROM Block is: 00000200

XIP Start at: 00002000
[COLOR="Red"]XIP size is : 0029DFFF
XIP Ends at : 0029FFFF
IMG Start at: 002A0000[/COLOR]

I haven't flashed but it looks better (whith the fixed one).

IMHO I have to check the option of write the new size of xip in MBR, is this right? Why it is not marked for default?

Thank you very much

PS: I have seen the new version. I will test it
[Windows Mobile] mac_es:
Hello,

Whith the refixed version:

Implantxip by ervius!!! (Fixed!)

ROM Block is: 00000200

XIP Start at: 00020000
[COLOR="Red"]XIP size is : 0027FFFF[/COLOR]
XIP Ends at : 0029FFFF
IMG Start at: 002A0000

XIP Inserted into: os.nb.payload

The start, end sections are correct but the xip size differs...
[Windows Mobile] ervius:
the xip length and end, is referred in MBR of payload, also if xip.bin is shorter, has to respect the structures, while if xip.bin is larger than 27FFFF, a message appear, and show that xip is longer to be inserted into payload, don't warry.... important is that IMGFS start is GOOD by the MBR structure ;)

but maybe I have to insert:

XIP size on Payload: 0xXXXXXXX

Xip Real SIZE in bin: 0xXXXXXXX

well, tonight other update for implantxip ;)

bye!
[Windows Mobile] mac_es:
Ok, could it be possible to adjust MRB if xip.bin is larger?

It is only suggestion for tonight impantxip :p
[Windows Mobile] mike1986.:
Please, anyone can explain me how to recreate packages from dumped os.nb.payload file? I'm using HTC Diamond with Ervius 9.4 kitchen and I want to replace 21232 XIP with optimized XIP by adwinp.
[Windows Mobile] bobsbbq:
Could someone who knows please explain how to use the xipporterex tool in the 9.3 kitchen? I have used a factory build 1.57 to get all my structures and OEMXIPKernel etc. I want to upgrade to the 1.59 version. It is not a native 0409 so I did not dump the whole thing but I do have the os.nb.payload and XIP.bin.

I have never used the porting tools here so a fairly detailed description would be helpful.
[Windows Mobile] ervius:
hey???

had you read in mymind?!!?!?!? ;)

all you are betatesters, so , download and try this new implantxip, that resize also imgfs section in payload and into mbr following the real size of xip.bin ;)

tell me if all works well....

download here and insert into tools\ folder of visualkitchen

http://www.sendspace.com/file/wiyzl9

byebye!!!!!
[Windows Mobile] mac_es:
Implantxip & Payload Resizer by ervius!!!

ROM Block is: 00000200

....................................
Preparing payload to be resized.....
....................................

Before:
XIP in Payload Start at: 00020000
XIP.BIN Target: size is: 00262DFF
XIP in Payload size is: 0027FFFF
XIP in Payload Ends at: 0029FFFF
IMG in Payload Start at: 002A0000
After:
XIP in Payload Start at: 00020000
XIP.BIN Target: size is: 00262DFF
XIP in Payload size is: 00262DFF
XIP in Payload Ends at: 00282DFF
IMG in Payload Start at: 00282E00

Payload resized and XIP Inserted into: os.nb.payload
...
ImgFs partition starts at 0x00282e00 and ends at 0x002a2e00
....
Writing imgfs to offset byte 0x282e00, sector 0x1417
Padding ImgFs from 0x499da00 bytes (0x24ced sectors)
to 0x49a0000 bytes (0x24d00 sectors)
Not conservative mode. Changing imgfsEnd from 0x2a2e00 to 0x4c22e00

Wow! The image looks right, I will try to flash asap

PS: I have readed your post about modifying nk.exe and if I understand it correctly the ram gain was because it was not reclaimed but in trinity there is only 64mb ram chip, and it reclaims 50 MB more or less.

So maybe instead of updating end ram to 84xxx a more conservative value could work?

xipport reports this

802ae000 - 802ae000 L00000000 Start: start of RAM
802ae000 - 802d4000 L00026000 initialized data of region_2 nk.exe
802d4000 - 802e0000 L0000c000 NUL
802e0000 - 802e6000 L00006000 uninitialized data of region_1 nk.exe
802e6000 - 802e6000 L00000000 ------ start of RAM free space
802e6000 - 83a00000 L0371a000 NUL
83a00000 - 83a00000 L00000000 End: end of RAM

cheers
[Windows Mobile] NRGZ28:
Hey erv... since you're working on xiporterex :)

Could we get an option to display the existing pagepool already set in nk.exe ? Or payload ? Currently... I have to change it to something else.. just to see what it was before :)

The ROM date.... It would be awesome if you could make the boxes where I can input the data manually instead of having to pick from the list of days.. months.. etc. I also notice that no matter what I change the ROM version to.. it always puts a 5 in the begging. IS that.. normal ?

If you could fix the ROM date/version to work on smartphones too it would be great :) Thanks :)
[Windows Mobile] Da_G:
Hi ervius;

Re: some of the extra files added during ROM compilation;

config.old

erviuspackages.zip

add2config.txt

build

add2config.txt should not wind up in the final ROM image should it? seems the kitchen is copying it because it resides in \packagename\files, should the proper place not be \packagename, next to app.reg, app.dat? (by the way the functionality of it works well, add2config.txt properly gets added to config.txt)
[Windows Mobile] anryl:
on kaiser no go the adresses on kaiser must be standard otherwise no booting the smallest imgfs start on kaiser is 340000
[Windows Mobile] Da_G:
Tried new implantxip on my raphael;

Results in a RUU error 270 after 100% on flashing, corrupt ROM

Then drops me right back into bootloader, w/ upgrade ROM code error
[Windows Mobile] ervius:
maybe we need an extra parameter on implantxip.exe:

-s 340000 for exaple, to suggest that imgfs minimum offset have to be 0x340000, so il xip.bin is shorter, it will be posizioned and some free sppaces will be stored before IMGFS start that have to be "0x340000"

;)

next release son then :)
[Windows Mobile] mike1986.:
I cooked ROM with new implantxip but my phone wont boot. HTC Diamond
[Windows Mobile] ervius:
okok, new version here:

http://www.sendspace.com/file/lhl0a7

added extra parameter (optional)

-s 340000, for example, if specified, lock min imgfs start at 0x340000 if xip lenght is smaller.....

try it also, I forgot in previous version fill xip section free space with all "FEFEFEFE" instead of alll "FFFFFF", maybe can cause problem.....

try it and tell me if boot now!!!

if continue with non-booting roms, maybe there is something else to realligh into MBR, ( for experts) you can check also ;)

bye!!!
[Windows Mobile] anryl:
just finished 21048 so upto 65 testing this new thingy :D

EDIT: -s 340000 working well here u did it again m8
[Windows Mobile] NRGZ28:
Hi ervius... earlier you said if we support your work more, you will continue developing the kitchen to be better, yet... you still completely ignore some of the posts in this thread.

For example... I posted about fixing some the english in the kitchen... Ignored. Posted about suggestions for xipportex... Ignored. Da_G posted about problems with the XIP, add2config... etc.... Ignored.

We made donations.... twice.... What else needs to be done to get your attention ? I can't continue supporting your work if I'm going to be talking to myself.

The least you can do is reply saying you don't want to do that stuff.... something.... Better than completely ignoring the post.
[Windows Mobile] anryl:
its the kitchen not working ? hmm i dont know but its working its better every new try and test . suggestions are not ignored but they are things that NEED to be working AND NOT NEED TO BE DONE NOW . just wait and see till its finished . :eek:
[Windows Mobile] makeveral:
I understand you but ervius is the best!! he updates the kitchen almost every day... and its an amazing kitchen!

I'd donate for what is done not for what will come.I'm also developer and is hard to answer everyone , fix everything etc... just be patient!
[Windows Mobile] hilaireg:
Donation

@ervius:

I sent a donation to this URL (the one in the kitchen)

http://www.bepe80.com/donation.htm

Please tell me that donation made it to you; or is it going to Bepe - and does he split it with you?

:confused:
[Windows Mobile] ervius:
implnatxip version 3:

http://www.sendspace.com/file/h33j2q

pratically, I forgot

1) to reallign also the FAT Start according with imgfs move;

2) to insert a check to reallign XIP size according with 0x20000 Xip ROM Block, maybe version 3 will be work ;)

p.s.: the last parameter is change from -s 340000 to -imgstart 340000

report if this version works well....

bye!!!

P.S.: the donation got to bepe (only to him!), and I'm happy for that, remember that he created the platformrebuilder, and also need to be supported by all of you ;)
[Windows Mobile] ervius:
shure, post all ;)

and try version 3of implantxip!

bye!
[Windows Mobile] Da_G:
Hi ervius,

new implantxip working good here on raphael, with no -imgstart param :)

Hmm, i take that back, i don't think it really injected the xip.bin, but rom still booted because of os.nb.payload containing compatible xip.bin already, here's the ouput

Implantxip & Payload Resizer by ervius!!!

IMG Min Value not specified..... continue without...
ROM Block is : 00000800

IMG Start is Shorter than XIP Start Exit...

I see, -imgstart is now a required value, assumes 0 without it, and 0 is less than xip start value :) trying now...
[Windows Mobile] anryl:
put 40000 as minimum then working :D
[Windows Mobile] Da_G:
my ULDR is not reduced (purposefully as using new 6.5 ULDR)

so min had to be 340000, no boot in that situation though

trying to take it one notch down from 780000 where it's at now, to 760000, probably need a similar minimum value for -imgstart

btw, could -imgstart be coded to be relative to some other value, rather than from start of file, because it varies depending if os.nb.payload is ULDR reduced or not.. maybe a minimum value for size of xip, for example

also, no boot on -imgstart 760000, so looks like needs to be -780000 (same as original os.nb.payload imgfs start)

edit again, working just fine with -imgstart 780000, which is same imgfs start as original os.nb.payload
[Windows Mobile] mac_es:
Here also:

imgstart is required, tried whith 40000

implantxip.exe -xip xip.bin -payload os.nb.payload -Imgstart 40000

Implantxip & Payload Resizer by ervius!!!

IMG Min Value: 00040000
ROM Block is : 00000200

....................................
Preparing payload to be resized.....
....................................

Before:
XIP in Payload Start at: 00020000
XIP.BIN Target: size is: 0027FFFF
XIP in Payload size is: 0027FFFF
XIP in Payload Ends at: 0029FFFF
IMG in Payload Start at: 002A0000
After:
XIP in Payload Start at: 00020000
XIP.BIN Target: size is: 0027FFFF
XIP in Payload size is: 0027FFFF
XIP in Payload Ends at: 0029FFFF
IMG in Payload Start at: 002A0000

Payload resized and XIP Inserted into: os.nb.payload

This is the same xip and payload that use before, it doesn't shrink. Whith the older version:

Implantxip & Payload Resizer by ervius!!!

ROM Block is: 00000200

....................................
Preparing payload to be resized.....
....................................

Before:
XIP in Payload Start at: 00020000
XIP.BIN Target: size is: 00262DFF
XIP in Payload size is: 0027FFFF
XIP in Payload Ends at: 0029FFFF
IMG in Payload Start at: 002A0000
After:
XIP in Payload Start at: 00020000
XIP.BIN Target: size is: 00262DFF
XIP in Payload size is: 00262DFF
XIP in Payload Ends at: 00282DFF
IMG in Payload Start at: 00282E00

Payload resized and XIP Inserted into: os.nb.payload

It is because of padding?

Thanks
[Windows Mobile] mac_es:
Hi,

implantxip version 3 is working correctly whith trinity.

It boots and everything works flawless.

cheers
[Windows Mobile] ervius:
yes, but I'm stupid.....

I inserted check to compare Xip start with Img start, but if -imgstart is omitted??? make ever this check, and ever the imgfs start is shorter....

I'll fix in few minutes ;)
[Windows Mobile] ervius:
version "final" (I hope!)

http://www.sendspace.com/file/q24x1d

also without -imgstart, now can continue inserting xip.bin

P.S.: also if uldr is untouched, if you reallign all inside MBR (IMGstart and FATStart) it has to work, maybe with proper limits (-imgstart 340000 or -imgstart 360000), important is that the implantxip reallign FAT start imto MBR.....

try it.

P.P.S.: is useless leave same -imgstart xxxx, like original stored into payload, all values into MBR will be untouched ;)

try +/- 20000 in -imgstart value ;)

bye!
[Windows Mobile] mike1986.:
Newbie question... If I'm dumping os.nb.payload and then replacing dumped XIP folders is it recommended to update this implantxip to newest version or I can base on this original one in 9.4?
[Windows Mobile] ervius:
yes is reccomended, becouse previous are bugged ;)

I think final version is bug free (I think..... :) )

try this:

implantxip version "final"

http://www.sendspace.com/file/q24x1d