yashsingh1/xdaforums huggingface dataset:
[Windows Mobile] djbeames:
Thanks. Does it matter if those are 'true' or 'false'? It won't affect the building of packages inside those 'pseudo-package' folders?
[Windows Mobile] utak3r:
I've checked only if enabling them will enable all packages inside - it didn't.
[Windows Mobile] djbeames:
That's all I really care about I guess. As long as "disabling" them doesn't "disable" all the packages inside... But if Enabling doesn't enable all, then I doubt disabling would disable all.

To Ervius: Thank you for this! I am enjoying your Kitchens more and more!!! If you could look into fixing this "cosmetic issue", I would be extremely happy!
[Windows Mobile] ervius:
I tryed to follow your discussion, but didn't understand....

in EXT packages there are:

device (for that build) packages;

device (common) packages;

Devices SHARED Packages.

and all works well, you can enable/disable all of them, what's the problem?
[Windows Mobile] djbeames:
Ok, I was going to screen shot this before, but finally did it.

In the attached screen shot, Exhibit "A" shows the folders that are inside <EXT\%DEVICE%\COMMON\>. Exhibit "B" shows the ACTUAL PACKAGES inside the folders of Exhibit "A". In other words, 1Herman is the actual PACKAGE, it is inside of 1Tweaks. All the folders in Exhibit "A" are merely folders holding the actual packages. There are NO PACKAGES inside Exhibit "A". All the PACKAGES are actually folders INSIDE the Exhibit "A" folders. So only Exhibit "B" are packages.

I would like Exhibit "A" to be hidden. These are not packages and changing them to 'True' or 'False' has no effect on packages included in the build.

That make more sense?
[Windows Mobile] ervius:
I see on screen in upper/right corner that you don't have EXT Build, why don't have U EXT build?!!?!?

maybe you didnt make attenction when I told ever and ever and ever and ever and ever and...... that to know exactly the ROM Structures, you have to dump an original "diamond" rom before?!?!!? ;)

btw, I posted in 1st post all my "Diamond" EXT packages, including:

EXT\DIAMOND\%Build%

EXT\Diamond\COMMON

EXT\Shared

Packages, all that I use, and all Enableable/disableable

download, unrar and analyze all "EXT" folder with all subfolders to understand how make all working on visualkitchen

bye!

EXT packages are avaiable also here:

http://www.sendspace.com/file/9kwms4

re-bye!
[Windows Mobile] djbeames:
LOL.. I liked the "re-bye!".. Very nice. I don't have an EXT selection because all of these packages are COMMON to all builds right now. I am building with 21500, 21501, 21502, 21215, etc. I don't want to have to copy ALL those programs (EXT Packages) to all those EXT Build # folders. That is a lot of wasted space in the kitchen. All my ext packages are "COMMON" to all build #'s in my kitchen. I can add a dummy "EXT Build #" folder to satisfy your point.

Our <EXT\%DEVICE%\COMMON> folders are setup the same. Except I have a lot more. I bet if you look in your kitchen you will see this:

SHARED-Devices: COMMON
-----------------------------------------------------------------------
TRUE Fixes Miei

Then further down (or up) in the kitchen window you will have:

COMMON:Fixes Miei
-----------------------------------------------------------------------
TRUE base_dpi_192_MIO
TRUE OEM_DRIVERS_FIXES
TRUE PhoneCanvas_Slider_Batteria_1_percento
TRUE Redist_dpi_192_Nuovo
TRUE Swater_192_Nuovo
TRUE xmanila_Configurazione_mia

See.. this is the same thing I have.. That first "SHARED-Devices: COMMON" is not needed. It's just showing you the sub-folders of <EXT\Diamond\COMMON>, you don't have any packages in that folder. THIS is what I am trying to say. It has nothing to do with my EXT build # not being there. (But i added it just because. :D

EDIT: I guess I COULD move them all back to <EXT\SHARED>, but I don't want to do that. That means they would be shared for ALL Devices, which is not what I want. I just want them to be SHARED amongst different builds of the same device.

EDIT 2 (AND FINAL): I apologize to you Mr. Ervius. You are far superior. After I added the dummy folder <EXT\Herman\21502> and selected it in the EXT drop down list, it made that "SHARED-Devices: COMMON" selection list disappear. THIS, could be a bug however. Just saying. I have NOTHING in that 21502 folder, but for some reason it made that selection list go away. Good Call. Thanks.
[Windows Mobile] daryelv:
7.0 -> 7.6 causing non-booting ROMS

I copied the 7.6 version of erviuskitchen.exe and the TOOLS folder into my kitchen and my ROMs stopped booting successfully. Was there a change in the folder structure that I need to account for from the older version to the newer version? I've built quite a few successful ROMs in this kitchen with the same SYS, OEM, ROM and EXT folders. I went back to 7.0 and things are working fine again.
[Windows Mobile] djbeames:
I went from 7.0 to 7.1 then to 7.6 and had no issues at any of those steps.

The only big thing that changed was the structure of the EXT folder. The XIP folder has changed some, but I am pretty sure its backwards compatible. Like almost every other new release, he changed/added the timebomb code, which would modify your xip. Dunno. Hope you have a backup of 7.0.
[Windows Mobile] ervius:
yes, but when I say that you have to respect the "EXT" (OEM ans SYS) structures, you have to respect them, also if in EXT build you insert a number like"11111", or "11112" ecc.... is important, the visualkitchen has to find all parts of structures, and shure, if you don't need "EXT Build" tou leave a fake build like "11111" empty, and insert all packagesgroups into "Common" or "Shared" folders ;)
[Windows Mobile] ervius:
btw in 1st post version 7.7 solved in part ext\device\build missing, if you don't specify a good or fake EXT\DEVICE\BUILD\ folder, it advice to you, and cannot build roms until you don't insert a: EXT\DEVICE\BUILD folder ;)

in tools\ folder of version 7.7, updated also my "implantxip.exe", (I created new becouse the bepe's one, was not compatible wirh some Smartphones payload to find right XIP Address into them), so you can see all values in hexdecimal, not in decimal, like in previous version!!!

bye!!!
[Windows Mobile] utak3r:
ervius, you may want to take a look at osnbtool, it's really powerful and supports almost every combination I've tried...

Here I wrote a little tiny tut about it.
[Windows Mobile] c3ro:
this sounds great! would be a great benefit, when Xipporterex supports the automated PagePool Changer for every device by this osnbtool-1.56.

**edit

latest version is osnbtool v1.58 .. am not able to download it, heres the original source , google translated here
[Windows Mobile] daryelv:
I'm going to try dumping the Stock ROM and rebuilding my kitchen that way. Usually I just copy over the erviuskitchen.exe and the TOOLS folder into my pre-existing kitchen (CDMA Diamond).

Ervius is getting these enhancement requests and bugfixes out so fast that I can't keep up with his latest code. The guy is a rom master and a pretty darn good coder too.

-Daryel
[Windows Mobile] utak3r:
This only tool can play as several other ones... all-in-one swiss knife ;)
[Windows Mobile] NRGZ28:
Well if this works to build smartphone ROMs now (I have not tried yet), you will definitely see that donation I promised!! :P
[Windows Mobile] NRGZ28:
Hi Ervius, running your latest 7.7 version :)

I wanted to make some suggestions that I think would benefit every chef using your kitchen :)

- Wonder if you could make the packages list a little smaller, so we can see more of what the kitchen is doing at the bottom. Currently, I believe, the information area at the bottom is way too small to follow it, as the ROM Is building. Would it be possible to detach the command prompt window ? Or maybe make the whole "information area" detachable in a separate window ? :)

- Also wondering if you could widen the package name area. Currenly almost all package names get cutoff. Maybe include some algorithm to auto resize them based on the longest name ? :)

- Maybe you can hide the DEVICE ID, Chunk and OS ID:. They're really not needed for us to see everytime, and.... we can't edit them in the kitchen anyway, so it seems like a waste of space :)

- Now in 7.7, for example, if I select "Raphael".... the EXT build automatically gets changed to 21215, but the XIP and SYS stay at 21042. It would be nice if you click on a build number and the rest would automatically be selected to be the same build number :)

- The ability to always keep the last line in the "information area" visible on the screen. Currrently, it doesn't scroll and you have the either click your mouse on it, or keep scrolling down.

- Finally.. the ability to also hide "common" packages, that usually never get changed :)

These are just some suggestions to make your kitchen even better, that's all :) Thanks :p
[Windows Mobile] daryelv:
This worked. I dumped the Stock ROM again using the 7.7 kitchen and copied over my EXT/OEM/SYS folders and my ROMs are booting again. Now to figure out why my Youtube isn't playing now with SYS 21215...

-Daryel
[Windows Mobile] Röchelhilpert:
it´s no kitchen problem. 21502/21215 are buggy ... try 21500/21501 ... maybe 21222 and it will work
[Windows Mobile] ervius:
I cannot use this tool, becouse, my payload reducer, with XIP Start mover from 320000 to 20000 offset, leave the header untouched for xip lenght, if I reallign the xip lenght with xipporterex, osnbtool, works well, but as I told, the rom doesn't boot, but if I leave the value, the rom boot well, but osnbtool, find an abnormal XIP size value and canno insert/extract xip from payload, for me, that love reduce in space payload and move xip start from 320000 to 20000 obtaining also about 4/5 Mb free more RAM on rom, this tool, for now is useless, maybe is good for extract, compress, and other, is usefull, but at moment there are also the immortal tools I ever used, the only one is that it reallign well all Sections, so if the xip from 3.5 Mb, became 12 Mb, it can insert and reallign MBR and IMGFS like a sharm, but meybe I'll insert this options into next release of xipporterex of visualkitchen ;)

btw is really a complete and usefull tool, greetings for the creator!!!

bye!
[Windows Mobile] mahjsa:
I have been playing around with this kitchen for a while now, but it's not as multidevice as said.

Just now I finished a dump from the latest Onyx ROM, but in the end the kitchen "thinks" it cannot dump the XIp from the payload. This seems a little strange. Yesterday I tried a dump from one of my own A701 image files and I got the same error. However I saw that from the (renamed) payload file, the xip.bin was already extracted. How is it then that dumpxip refuses?

One more item: it seems that boot.bat has problems with Windows path names when spaces are present. I had to put "" around it.

I played a little with the dumpxip.bat and found that for extracting an A701 rom the following edited bat files works. (However from the kitchen dumpxip.exe is called.

@ECHO OFF
if "%~1"=="" goto :usage
set path_exe=%~d0%~p0
set path_arg=%~d1%~p1
cd /D %path_arg%
"%path_exe%imgfs\dumpxip.exe" "%~1"
if not "%errorlevel%"=="0" goto :mstools
goto :EOF
:usage
echo Usage:
echo dumpxip.bat ^<.nb.payload^>
pause
goto :EOF
:mstools
REM Try if msflshtool will extract a xip
REM on A701 it's part1
"%path_exe%imgfs\msflshtool.exe" "%~1" -d -p 1
REM Rename file to xip.bin
ren "%~1".part1 xip.bin
REM and run dumpxip again
"%path_exe%imgfs\dumpxip.exe" xip.bin
if not "%errorlevel%"=="0" goto :error
goto :EOF

:error
echo.
echo ERROR! (errorlevel: %errorlevel%)
pause

So maybe it's possible to put this into kitchen to have a wider range of device to use it for. (Hopefully ending with a truly multilang/multidevice/multibuild kitchen.:)
[Windows Mobile] utak3r:
I'd rather go for staying numbers as they were before changing device - because there might be a situation you want to select different XIP and SYS (not to mention EXT)...

As for the rest of your requests - I double them :)
[Windows Mobile] ervius:
I said multidevice, becouse for a lot of "HTC" devices, it works well, I never said "Universal-Device" ;)

btw, good trick, I inserted into bat, when I'll update again the kitchen I'll post :)

P.S.: with bat files, runned by visualkitchen you can do everything you want, great is the power of bats files, cos I Leaved them into, so you can play with them and modify, and make better all!!! ;)

I have only a Diamond, but people like mahjsa, with little modifications on bats files, can make visualkitchen real "universal-device" ;)
[Windows Mobile] mahjsa:
:cool:Molto grazie Ervius, forze conosce anche Elminster (from Poland) because he has made great kitchen for A701 based on Bepe/yours. I wait for next version so I can play a little more.

:DBTW I now have a working version WWE build 21222 AKU 5.01 for my A701. On to the NLD version!
[Windows Mobile] ervius:
nope, I don't know him, but can know ;)

btw version 7.8 at 1st post, added your script and a checkbox to excange between big or small dos prompt window when build rom ;)

bye!!!
[Windows Mobile] mac_es:
Hi ervius,

I'm getting this line when preparing packages:

ERROR!!! Found Module duplicate on Module...

though after that everything is running fine. Could you make more explicit the message? I mean, can you write the name of the module to track down the error?

Thanks
[Windows Mobile] Krzysiec:
What does this "LZX Compression" mean ? Because if i check the box or if i uncheck the box ... my final nbh file got same size ... Or is that for certain systems or device to use ? I`m using WM 6.1 os ... Thanks for reply :)
[Windows Mobile] DaveShaw:
utak3r already answered this :

http://xdaforums.com/showthread.php?p=3712097&highlight=Compression#post3712097

Ta

Dave
[Windows Mobile] utak3r:
...although the resulting nbh file should be smaller with LZX than with XPR...
[Windows Mobile] ervius:
is not important, like error, is only an advice, to see duplicate files/modules inconutered, only have to check "advice on overwrite" and before build rom, if there are some files/modules that overwrite yet existing ones, it shows a list of them.

into the lists, UPPERCASE are modules, lowercase are files ;)
[Windows Mobile] Krzysiec:
Maybe i`m stupid but i cant compress my ROM with LZX ... Do i have to change packages in some way ? After lunch packages after chose DEVICE: Diamond ... on the bottom i get message:

Info about Device: DIAMOND Found.....

DPI in use: DPI_192...

RES in use: dpi_192_resh_480_resv_640...

Langs Found: 0415

Changeing to: DIAMOND Device

Reenabling all skipped packages.....

All packages Reenabled!!!

ROM Is Compressed in XPR Mode!

And then after tick box next to LZX compression and Cook ROM size of ROM is the same :/
[Windows Mobile] ervius:
XPR Compression: Nbh was 110 Mb

LZX Compression: Nbh is 95 Mb.

only have to flag "LZX Compression.

maybe the process doesn' end successfull, and you see the same old nbh file
[Windows Mobile] utak3r:
well, no... it should work just as it is :confused:
[Windows Mobile] mac_es:
Thank you, very much. It was the custsat.dll module...

Though I have in my EXT\TRINITY\<build> a package which overwrites TaskMgr.exe and it doesn't show the error.

The custsat.dll package is in EXT\SHARED

I know that is overwriting TaskMgr.exe because platformRebuilder is saying so, and if I left TaskMgr.exe as file (in EXT package) and tries to overwrite the module in SYS platformRebuilder crashes.

btw, which are the diffs between leaving a file as file or as module?

Thank you very much for your utilities.

cu
[Windows Mobile] Krzysiec:
So thats very very very strange ... I make everything like U`ve said here Downloaded 7.8 kitchen ... Copied Tools and .exe ... Open kitchen ... chose device (packages are loaded) than tick the box next to LZX ... and ... cook ROM ... After that ... still same size ... Was 114 MB before and is 114 after ... :( I give up ...

And why afterload packages this text appear:

Info about Device: DIAMOND Found.....

DPI in use: DPI_192...

RES in use: dpi_192_resh_480_resv_640...

Langs Found: 0415

Changeing to: DIAMOND Device

Reenabling all skipped packages.....

All packages Reenabled!!!

ROM Is Compressed in XPR Mode!
[Windows Mobile] ervius:
that's only an unfo about original compression found on payload file.
[Windows Mobile] Krzysiec:
That`s very strange ... I tried everything ... BUt size remain the same ... with LZX or without :( But the worst is that i`m only one who cant get it work ... I`m run out of ideas at the moment :/ When tick lzx this: Enabling LZX Compression..... is pop up on the bottom but after press cook nothing have changed :/ Maybe i`m make something in wrong order ?
[Windows Mobile] ervius:
double....
[Windows Mobile] Krzysiec:
Maybe it`s because of Vista using ? :/ Or it doesn`t depend of it ?
[Windows Mobile] anryl:
dsm

set DSM=b5332311-48f1-4b76-ad70-8efa5db8fa3a.dsm

what is this one for ?
[Windows Mobile] ervius:
this is default MSxipkernel dsm for smartphones, don't warry, all works as it has to work!
[Windows Mobile] mahjsa:
Sorry for keeping bugging about the xipporting and extracting, but I really would like to work for my device with this kitchen, it seems easier to put in or leave out packages than the one I am using right now. (Bepe's 6.xx kitchen)

Talking about MSXipKernel, I am still having problems getting the xip's extracted or ported. It is very unclear how this xipporterex program goes about extracting and porting the xip's. Biggest problem is to change or set the date of the os.nb.payload and to push the button PortIt.

Allthough when I manually extract the xip.bin with msflshtool and next put it in dump_xip.bat all works OK, but in kitchen's xipporterex it doesn't work and it is therefore impossible to do the porting trick....

(Until now I understand that I have to keep the OEMxipKernel files original I can use the MSxipKernel files to update my device's xip. Right?)

But how to build a xip if the program in kitchen don't work properly?
[Windows Mobile] Da_G:
To port xip, i've just been using the kitchen to dump stock RUU for my device...

copy or rename /ROM/devicename/buildnumber to /ROM/devicename/newbuildnumber

then bring in new /ROM/shared/newbuildnumber/msxipkernel

that's pretty much all that's required :) the rest of components of xip (romhdr.bin etc.) are all dumped by kitchen.. so no need to further mess with xipporterex.. unless u want to reduce size of ULDR, etc.

XIP is dynamically generated using these source files every time you cook a ROM, so it has worked great for me so far :)
[Windows Mobile] ervius:
why do you tell about, if never tryed???

did you see into rom\device or rom\shared after xip porting with included visualkitchen xipporterex???

xipporterex, write new xip..bin into rom\device\payload file, and add new xip build folders into:

rom\device\build\oemxipkernel (with original oemxipkernel of device),

and

rom\shared\build\msxipkernel folder picked up from new xip.bin extracted and ported.

only a bug on visualkitchen after this operation, you cannot see the new xipbuild, bug, solved with 7.9 version at 1st post!

guys, I think that for me, if you don't try better and use more my visualkitchen before ask for useless question, I'll never answer to you about them.

if you check better before ask, you'll see that the answer are into visualkitchen

1st post version 7.9 and after xipporting new xip builds only have to choice it on xip build into visualkitchen.

bye!
[Windows Mobile] ervius:
little infos:

I tryed (stressed) some the osnbtool.exe, and works well except for uldr reducing.....

I explain:

if I extract uldr (part 0) and with an hex editor I reduce it to 128 kn (1ffffff) in lenght, to respect rom blocks size, if I reinsert it into payload, osnbtools writes well rom header, and if I insert also the xip.bin reduced, I see in mbr of payload that all is ok, but like I told some time ago, if I don't modify mbr leaving xip.bin size untouched (so never I can reuse osnbtool to reinsert or dump xip from payload!), the rom, after build doesn't boot, and stucks into boot mode, so , if you use xipporterex to reduce uldr/xip.bin into payload file, then cannot use anymore osnbtool, until the author will provide to insert some little algos when uldr/xip was reduced and reinserted into payload file with his "real great" osnbtool

bye!
[Windows Mobile] anryl:
implantxip from 7.8 kitchen did messed up the rom

from 7.0 working perfect :confused:
[Windows Mobile] utak3r:
Guys, do you know if there's a possibility to turn xip building off in platformrebuilder, so it would go straight to copy os.nb.payload and do imgfs stuff?
[Windows Mobile] c3ro:
hello,

am having a simple but annoying problem. probably someone can give me a hint.

my problem is, that after sys-changing and building rom, the boot comes with 2 times a signal instead of just one time (you know the beep before it says: Tap the touchscreen display to ...)

The calibration and stuff going fine, but then setting up the "Date & Time" is the standart one and not the one i setup with visualkitchen.

it shows 22.08.2008 instead of 05.05.2009

I guess its related with the .ROM module.

When i process a new SYS build. i copy the old SYS and insert in there all stuff from new build, except the .ROM, that i leave from old SYS.

C:\kitchen\SYS\19965\SHARED\COMMON\.ROM

C:\kitchen\SYS\21042\SHARED\COMMON\.ROM (the same)

would be very kind, cuz im getting nuts ^^
[Windows Mobile] ervius:
maybe you need old implantxip.exe by bepe and also insertxip.bat of old version of visualkitchen, can you share payload and xip.bin???

bye!
[Windows Mobile] ervius:
you can also delete ".ROM" module, platformrebuilder creates new one.

isn't it the problem, the date is hardcoded into nk.exe module, maybe xipporterex is not quite compatible in this case with your xip.bin (nk.exe)

post the nk.exe module or intere xip.bin.
[Windows Mobile] utak3r:
ervius, could you enable in xipporterex setting PP to non-integer value? I'm using 3.5 (0x38) PP in my ROMs and have to modify it by hand...
[Windows Mobile] c3ro:
hi,

thanks for answer.

yes, i wrote a bit of nonsense after some thinking, sry.

i just realised that its always keeping the old "date & time" in payload.

anyways, i send you the nk and xip.bin's

http://rapidshare.com/files/229616330/loged.rar

am also having a wierdo message, when trying to reduce a payload; ImgfsFromDump.exe complains that it couldnt find MSVCR71.dll .. first time im trying these the visualkitchen on vista and it just worked fine at first glance, and now this *grr

thanks ervius!
[Windows Mobile] anryl:
it was booting fine but all graphics were mixed up

and the date off rom was back to 2008

http://rapidshare.com/files/229617209/KAISER.rar payload rom xip.bin
[Windows Mobile] ervius:
btw version 7.9 v2 at 1st post, some little bugs on xipporterex to find xip start/end and also for implantxip, for the rest, I'll analyze some tomorrow or soon.

bye!
[Windows Mobile] ervius:
I analyzed both nk, pqayload, xip.bin, and all seems work well, maybe there are som escripts (provxml, or xml, or apps, don't know.) that sets date/time back.....

bye!
[Windows Mobile] anryl:
its the imlantxip.exe its making something diferent that the xip is not right on kaiser :cool: gona use the older one no big deal

i tried the 7.9 rev2 but the same result with the graphics and date

how is this new one working is it still taking the created temp xip ? or is it taking the xip files somewhere else i dont know why is the xip different by using the new implantxip.exe
[Windows Mobile] ervius:
my new implantxip reads rom block, take frm mbr the xip and imgfs start into payload, so, from xip start and imgfs strart, there is xip length, it takes xip.bin by this values, is strange that xip isn't right, it must be. I'll try on payload posted by U, but it have to be right, or maybe is compressed, but xip.bin is that!
[Windows Mobile] anryl:
ok this is the xipbin and romhdr from temp created working with old implant
[Windows Mobile] johnpatcher:
Are ROMs created with this kitchen protected in any way? I have dumped a stock rom, and just re-cooked it, but if I try to extract it using the "normal" (old-fashioned) kitchen, the folders (OEM, SYS, XIP) are just empty, so there must kind of protection?

How can I disable it?