Related
Hi,
unfortunately I am not able to implement a new *provxml to a new ROM.
I know http://forum.xda-developers.com/showthread.php?t=398025
and some other threads, but all my entries (Mailaccounts, WiFi informations - which I got with rapiconfig) are not in my new ROM.
I am doing somewhere a mistake. It does not work:
I have done the following:
1. created an acconts.provxml
2. renamed to _setup.xml
3. Created an OEM package with Ervius Package Creator.
Have now 5 files in the OEM folder: _setup.xml, *.rgu, *.dsm (size 0k), option.xml and initflashfiles.txt
4. Moved option.xml out of the OEM folder
5. Drag and drop OEM folder over BuildDSM.exe. This creates a new *dsm (size 1k)
6. place back option.xml in OEM folder
7. copy OEM folder under \Packages - i have tested also the OEM folder
8. cooked and burned ROM
Does someone has a OEM package with a *.provxml (including email2 and wi-fi infos). All imported emai-addresses and wifi info van be deleted of course. ?
If I use "rapiconfig.exe /p _setup.xml" all my infos are ok.
Any help is welcome.
Regards
kuzco1
this is what works for me...
you have to name it:
mxipupdate_zz_oemoperators_100_PPC+All_filename.provxml
you can replace 'filename' with whatever you wish.
(there should be no space in provxml, this editor isn't working right for some reason)
let us know if this works for you...
joemanb said:
this is what works for me...
you have to name it:
mxipupdate_zz_oemoperators_100_PPC+All_filename.provxml
you can replace 'filename' with whatever you wish.
(there should be no space in provxml, this editor isn't working right for some reason)
let us know if this works for you...
Click to expand...
Click to collapse
Hello,
what do you really mean ?
I have renamed my _setup.xml to mxipupdate_zz_oemoperators_100_PPC+All_filename.provxml and put this file \OEM\OperatorPKG. After cooking and burning my Kaiser does not boot any longer - I have to reverted to my old ROM.
Regards
kuzco
have you tried creating a cab file with your _setup.xml?
see if that works, maybe your xml has errors.
as far as creating a dsm, all I did was drop the file into another oem folder that already had some provxml files.
the fact that your phone won't boot now would indicate to me that after the filename change the file is indeed being processed, but the xml has errors.
download the 'tmobileforromcooks.zip' file in the following post and compare the provxml files with yours.
http://forum.xda-developers.com/showpost.php?p=2237367&postcount=1
good luck
joemanb said:
have you tried creating a cab file with your _setup.xml?
see if that works, maybe your xml has errors.
as far as creating a dsm, all I did was drop the file into another oem folder that already had some provxml files.
the fact that your phone won't boot now would indicate to me that after the filename change the file is indeed being processed, but the xml has errors.
download the 'tmobileforromcooks.zip' file in the following post and compare the provxml files with yours.
http://forum.xda-developers.com/showpost.php?p=2237367&postcount=1
good luck
Click to expand...
Click to collapse
Thanks, but this zip does not work either. I will play more ....
kuzco1
hint hint: Try adding these settings to an already existing prov.
as i read somwhere you cannot add any provxml file in a dumped rom! but u can change and add reg edits in an existing provxml file. and theres another thing i think you should know: provxml files are the last reg based files that will get written in the cooked rom SO they have the ability to change and overwrite rgu files that you created if they both have the same reg path but diff values.
Hello everyone, put my old kitchen, a little 'restored.
IMPORTANT: To build a good rom, you 1st have to dump an original rom for your preferred device, to have all files needed to build it after (header.xml, splash.xml ecc...)
List of Features:
Check rom version for exchange for new payloads (tested on hd2 rom 3.14 and it worked!), some minor adjustments, the editor, RGU, app.ref etc ..., now always starts as an administrator.
to test it, dump an original rom and then have fun customizing!
New style, new tricks at runtime, new tools for dumping and building !!!!! (Libnb.dll!)
Fixed bugs on inclusion radio.nb and splash.nb !!!!!
Import into .\ext, old-style packages, OEMpack, EXTPack (and also from Cab files
in the context menu is also remodule package (from files to module!) and re-file package (from modules to files!); other bugs solved!
Rapi connection problem solved with device in activesync and remove ring tones, images by default!:
Feature on delete files (ringtones, images (wallpapers) and other images (avatars) from a folder in oem \ langdevice \ .....)
Features to all feedback packages, from kitchen and easily editable text file (packages_usefull_infos.txt) in the root of the kitchen.
Can also import "rebuild dumped roms", from DFT dumped, OSkitchen kitchens and RAW Dumped roms!
Support to run the cabs charged by hands at 1st boot after flash!
Save & restore all tweaks in all the tabs when save/load a rom!
Added info exchange Rom language and Rom on the first use of header.xml libnb.dll nbh file to create!
Added new feature to force the run provxmls in Rom
Now when a dump .NBH, the new build is imported, in your EVK in use!
.\TOOLS folder
Inside the folder .\tools, you will find a new folder: registry_tweaks. The .\registry_tweaks folder includes some sample files. Replace and/or add .REG and .PROVXML files, name the files properly and the .REG files will be added as registry entries, the .PROVXML will be renamed as ****. ZZZZ_ provxml, as files are added. provxml, precisely in the rom and run when you first start to customize the rom as you like
The kitche includes two context menus for adding new .REG or .PROVXML files, edit them or delete if unused one!
Also includes new versions of DSM_editor and implantxip (no fake virus info about, someone in previous version, not me, inserted automatic "admin execution" with a kind of utility, into my implantxip.exe!, and maybe that "trick", was detect as fake virus, now, with my original updated version of implantxip.exe, my kaspersky doesn't find anything!!!!!)
Note
DSM_editor and implantxip (no fake virus info about, someone in previous version, not me, inserted automatic "admin execution" with a kind of utility, into my implnatxip.exe!, and maybe that "trick", was detect as fake virus, now, with my original updated version of implantxip.exe, my kaspersky doesn't find anything!!!!!)
System Requirements.
.NET FRAMEWORK 4.0 to execute new version of visualkitchen and new tools inside (dsm_editor and implantxip!)
Version History
12.2.9: compatible with x64 system machines, was libnb.dll,not was dll, was my exe, only I had to force x86 execution, also on x64 machines, that version was only for x86 machine, now at runtime, it is recreated, if is x64, compatible version is putted into .\tools folder, else a x86 compatible version will be copyed into .\tools folder!!!
12.3.7: package creator added as optiona choice when wanna import a cab into packages!
12.3.7: Added option to turn tricks "reg" to be placed in rom that will be in a good provxml 'forced to be the last to be executed, overriding any settings from other taxes proxml !!!!!
12.3.7: when forced execution provxml, reg cab, the sequence is .PROVXML in Rom, .PROVXML uploaded by you, proxml derived from the reg trick and finally the cabs
12.3.7: added possibility to add and execute a .tsk file into ROM!!!
12.3.9: bug solved on provxml creation when found "delete regkey" or "delete regvalues"
12.4.3: bug solved on save and load roms, new icon for exe!
12.4.3: "reloaded" update pagepool options on new implantxip.exe
12.4.4: solved problems with implantxip value as default
12.4.5: inserted possibility to load, edit and delete mortscript scripts into rom to run (config.txt will be populated with selected scripts) at 1st boot!
12.4.8: when you choice a bmp to became a splash screen, the kitchen automatically check if the format and size is good, if not, automatically modifyes the image, makeing before a backup of it, and adjusts it according to the file "splash.xml"
(I suggest to redump an original rom for your device, becouse there are a lot of libnb.dll, and I've changed in times, so maybe splash.xml, could be different in format!)
12.5.0: updated package_creator, see and edit into \tools folder user_folders.txt to add your own modded folders into start menu for lnk files extracted by cab files; now, all manila-language files will be stored automatically into relative 04XX subfolders, so only real lang-manila files needed will be stored into rom, and before build, cfc_gui.exe will be executed to compress and patch manila, if you want, only have to click on "tools<>patch manila", on cfc_gui.....
see U!
12.5.2: new built of implantxip, and some little little improvements on erviuskitchen.exe!
12.5.3: Added Visual advices for packages that have to be recmode or reversemode!
12.5.6: re-file or re-module packages that you insert into comments like "remodule, or re-file! (only id relative poackage is enabled while build rom!)
solved little bug on packages colouring (same color on "false/true" packages (enabled/disabled!))
12.5.8: solved some trubbles with LZX Compression!
12.6.0: more compatibility with new xipporterex to change rom version on nk.exe into 3.14 TMOUS ROMS! and now recontruct better alla lang files/folders for manila!!!!
12.6.2: Full compatibility with all Language codecs to recontruct well all lang files/folders for manila, and also all MUIS files will be stored in relative language SubFolders!!!
12.6.3: only exe, now remove also all *.cpr files with resolution different thankn used by your device, and store all of them into :\moved\cpr_moved\namepackage\resolution\...
Download Link
http://www.4shared.com/file/0Nv3ETFr/VisualKitchen_12_5_8.html
Updated only exe! (12.6.3_rev2)
http://www.4shared.com/file/9yFFf6YA/erviuskitchen_12_6_3_only_exe_.html
Quick Thread Link
Discussion on Latest kitchen start here: http://forum.xda-developers.com/showpost.php?p=9500214&postcount=2484
Reserved for future expansion
OLD visual multilang/multidevice/multibuild kitchen for last bepe rom-tools!! V1.8.2
Hi, this is a visual multilang kitchen based on last bepe's tools to build a rom.
Last Version: 1.8.1 aka 10.8.1 (1.8.1)
Date: 28.07.2009
Download Links: 1.8.1, 1.8.2
new_visualkitchen_v_1_8_1_only_exe_+_Tools_folder.rar 7MB
erviuskitchen_1_8_2_fixed.rar 523 KB
Latest version of Ervius Visual Kitchen tools. New visualkitchen with all dsm/rgu recreations/updater to have complete old_style roms ready to use .pkg updater!!!!! The KITCHEN has been updated to include logging; (see build_log.txt into root of kitchen after built a rom!!!)
Note: Also attached to this post as <filename>.RAR.ZIP. After download, remove (.ZIP) before UnRAR'ing.
Changes In This Release:
XIPPORTEREX:
Added compatibility with new 2.09 kn.exe to r/w correctly date/version on ROM!
Added capability to find version/release_date on new wm 6.5 nk.exe!!!
DUMP Process:
Now if dump a stocked rom, in EXT packages it leave relative dsm/rgu, create a global packages.ini (with all dsms infos inside!) and for each EXT Package, create "package.ini" file, with all infos about relative dsm,
All shadows, depepndencies, certificate needed in .\tools folder, it populate "dependencies" and "certificates" folder with all dsms and certs files found during dump process, used to insert/edit all dsms into rom with dsm_editor
OTHER button:
Provides for selection of ULDR reduction, PagePool sizing, disable Certificate
Verification, etc. Settings are stored in: ERVIUSKITCHEN.INI.
Editor:
Addresses issues when using "editor".
Compilation:
Solved bug on 6.5 reak aku roms
Addresses issues when searching structures and duplicate files during compilation.
Added possibility to change max number of modules in an hybrid ROM (nk.exe from 6.1 kernel and XIP From 6.5 kernel) the value is saved on that rom configuration, so every rom loaded has his max-modules value setted
Extraction:
Addresses issues when extracting contents of some device .NBH/.NB files.
Compatibility:
Addresses unsupported Language code (ex: 040C).
Added compatibility with old style rom (IMGFS & XIP).
All modules can be reallocked.
DSM processing; all dsm and rgu are updated/created -only with old_style roms creation! (required for cab.pkg updater support.)
In old style ROM mode; all is executed automatically, XIP porting is automated:***
- Correct realtive device's .VM must be copied to .\OEM\<devicename>\.VM
- Correct XIP.BIN must be copied to .\ROM\SHARED\<buildnum>\
Post-Download Instructions:
Extract the contents of kitchen archive to the root of your hard drive (ex: C:\XDA) to avoid path length errors.
Backup existing kitchen files. Files/Folders to backup are:
- Files in root of kitchen (ex: C:\XDA\My_Visual_Kitchen)
- .\TOOLS folder
Remove (delete) ERVIUSPACKAGES from TOOLS folder (ex: C:\XDA\My_Visual_Kitchen\TOOLS\ERVIUSPACKAGES).
Copy the contents of the extracted archive to the kitchen (ex: C:\XDA\My_Visual_Kitchen\) folder.
----------------------------------------------------------------------------------------------------------------------------------
Implantxip.exe (Pagepool Patcher/changer!)
Download Link: implantxip.rar 166 KB
implanxip can works with:
all kind of payload file, and more:
if a payload has ULDR removed (ULDR part not present!), it can work on it and reallign well some bytes into MBR
you can also remove completelly the uldr section (you could save some more space into payload in this way! (be attenction: in some payloads this operation causes non-booting roms!!! make a backkup of original
payload before use: "-uldr tryremove parameter!!!)
for help about: in prompt command write: implantxip /h )
Note: Also attached to this post as <filename>.ZIP.
----------------------------------------------------------------------------------------------------------------------------------
EXT Packages Rebuilder
To build EXT_Packages from old style ones; use the tool at your own risk!!! Fixed lost modules into new package created, now all modules are into .\files subfolder after ext package is built.
Download Links:
EXT_PAckages_rebuilder+Structurer_all_lang_enabled_v3.zip 8 KB
EXT_PAckages_rebuilder_modules_fixed.rar 9KB
Note: Also attached to this post as <filename>.ZIP.
Excellent work as always ervius.
Grazie mille.
^.^
That might come in handy for some ppl.
For my part, I'm used to command line as my primary WS is linux based. As a matter of fact, i prefer it.
@Ervius: Do you have any experience in coding for unix/linux?
At some point, pof coded a htc-flasher kitchen, but it was mostly wrappers for the windows programs.
Most of the tools we use for ROM building have their source code available, so...
Anyways, I'm off.
A.
GREAT!!
I'm testing it in my kitchen just today. I'm looks fantastic. Thanks!!.
If now you can integrate your XIP porting tool then.....
Regards,
elparra72 said:
I'm testing it in my kitchen just today. I'm looks fantastic. Thanks!!.
If now you can integrate your XIP porting tool then.....
Regards,
Click to expand...
Click to collapse
this is a alpha version, and stucks on platformrebuilder.exe execution, , but when I have some time more maybe insert all inside, xipporterex and other tools of mine!
can you post it on rapidshare please, megaupload is a menace. thanks.
In any case this is a great work!!.
I've been checking folders structure and adapte it to Spanish (or another language) is really easy. I'm preparing a new ROM, but as soon as I post it in a Spanish site, I'm going to 'play' with this application and l'll inform you about troubles. Thanks !!
On the other hand (I know this is not the best post to speak about), Your active sync killer is not working fine in 2.xx ROMs. Are you preparing a new one? Do you have a solution?. Thank a lot in advance.
Kind regards!!!
El Parra72
elparra72 said:
In any case this is a great work!!.
I've been checking folders structure and adapte it to Spanish (or another language) is really easy. I'm preparing a new ROM, but as soon as I post it in a Spanish site, I'm going to 'play' with this application and l'll inform you about troubles. Thanks !!
On the other hand (I know this is not the best post to speak about), Your active sync killer is not working fine in 2.xx ROMs. Are you preparing a new one? Do you have a solution?. Thank a lot in advance.
Kind regards!!!
El Parra72
Click to expand...
Click to collapse
you can adapt, but add other languages, near 0409\ and 0410 folders you can add 04xx\ or o8xx\ all you want, the kitchen at start recognizes how many into, and show all into combobox, you only have to choice in witch language want build the rom
for activesync killer, what you refer to, mine or the original by eliasweb???
bye!
I've detected this trouble in both. I've test them in several ROMS based on 'oficial' v.2.xx. I'm going to look for your post and follow this trouble there. Thanks.
..................
this looks better and better. I dearly hope that it will come with some kind of manual.. anything... just to know what to press and which button does what...
Thanks!
mjaxa said:
this looks better and better. I dearly hope that it will come with some kind of manual.. anything... just to know what to press and which button does what...
Thanks!
Click to expand...
Click to collapse
visual kitchen version beta1 released at 1st post, and see all ROM\ structures.....
Hi ervius, thanks for your tool.
I was trying beta1.
I have a couple of questions:
i've tried to import a package (generated with package creator) , I browse to the folder containing it, but after the right-click-> import package, it doesn't appear in the list of the applications.
I see it has been copied to the EXT folder but nothing more.
Also importing a package resets all the choices I made on what packages to include/exclude
If you need more details just ask
Thanks
A.
very nice, I will test this this week, and see if i notice anything. once again thank you
andreapappy said:
Hi ervius, thanks for your tool.
I was trying beta1.
I have a couple of questions:
i've tried to import a package (generated with package creator) , I browse to the folder containing it, but after the right-click-> import package, it doesn't appear in the list of the applications.
I see it has been copied to the EXT folder but nothing more.
Also importing a package resets all the choices I made on what packages to include/exclude
If you need more details just ask
Thanks
A.
Click to expand...
Click to collapse
well, well, so, some bugs are detected...
continue ti test it
Hi
I dump a rom (use:1s streps of Surface Kitchen v1.01), now i have "sys", "oem", and "rom" folders. Were i put this folders in your kitchen?
first steps!!!
ruipgouveia said:
Hi
I dump a rom (use:1s streps of Surface Kitchen v1.01), now i have "sys", "oem", and "rom" folders. Were i put this folders in your kitchen?
first steps!!!
Click to expand...
Click to collapse
Check the screenshots. You'll see the directory structure there.
ruipgouveia said:
Hi
I dump a rom (use:1s streps of Surface Kitchen v1.01), now i have "sys", "oem", and "rom" folders. Were i put this folders in your kitchen?
first steps!!!
Click to expand...
Click to collapse
use bepe's packagebuilder.exe on a dumped rom, after use my EXT_PAckages_rebuilder+Structures_rebuilder (attached here!) on dumped rom, finally you'll have all rom structures ready to be koocked by my visual kitchen!!!
bye!!!
P.S.: at first post "beta 2" is ready (some bugs solved!)
Hi!
There a lot of kitchens avaialable for ROM building. Now this one is to ease TouchFlo3D building.
This kitchen uses the knowledge and works of 6Fg8, D-MAN666, xboxmod, chainfire and many others who are involved in Manila hacking.
If you use this kitchen and/or any of the decompiled scripts then be so kind and share back the source code of your modified scripts too!
This kitchen (v1.5) has the following utilities included:
6Fg8's mode 9 editor (v3.3.0.1)
sztupy's mode9 converter (v1.0)
chainfire's CFC compressor (v0.46)
MKT: a tool for batch converting/compressing/compiling mode9,qtc,png,xml,lua files (v1.1)
LuaDec (2.0)
A work in progress lua and xml IDE
And various other tools
In the center of this kitchen stands MKT aka manila_kitchen_tool, which is like 'make' but for manila kitchen developement.
It has the following functionality:
split hased _manila files back to their original filenames
join a bunch of files in a directory back to their hashed form
mass decompile mode9 files back to xml and save their lua scripts
mass convert qtc files to/from png files
mass compile lua files
It works like 'make' in sense that only the modified files will be recompiled/recompressed so after the firts setup it might be ideal for manila development.
The output of the kitchen was tested with the Rhodium manila (WVGA version) on a HTC raphael device and it works, so this project is no longer a prototype, but is still considered beta stuff
Kitchen set up
I uploaded a complete Rhodium2 Manila kitchen in case you want to use that as a base (download both the kitchen and the rhodium files, then copy them to the same directory), but of course you can use any other manila pakcage you get across. To set up the kitchen copy the package into the 'pkg' directory then run:
Code:
mkt split
to split the hashed files back into their filenames. (For this conversion it uses the same table as m9editor uses.)
You will get a "bin" directory. This will hold all "compiled" stuff, so here you will find all the files that don't need more preprocessing, and can be hashed/installed to the device
Next you want to get some editable files out from the luac, mode9 and qtc files, so use:
Code:
mkt -x bin frommode9
To decompile mode9 files back to XML (it will also extract the scripts out of the package)
Next:
Code:
mkt -c d,qp fromqtc
or
mkt fromqtc
Will convert all qtc files to png files. (the first type will work on cfc compressed qtc files, the second will work on non cfc compressed files)
After this only the scripts are remaining. Unfortunately these can't be decompiled easily, so grap the decompilation of someone (like me ), and put these files into the "insrc" directory. After this run
Code:
mkt -d insrc -o src split
so all the hashed _manila files will be converted back to their original filenames to ease searching through them.
After this you're ready with your prepared kitchen. These things were already done with the Rhodium manila so you might use that package to start manila modding.
Compiling
You can use tomode9, compile and toqtc commands to compile these files back to their binary counterpart. Alternatively you can use:
Code:
mkt -c pq,c,p make
to run this three command after each other. It's like a Makefile, so it will only compile things that have changed. Of course you might want to 'make all':
Code:
mkt -a -c pq,c,p make
This will build all files from the "src" directory into the "bin" directory
Creating the package
After you're done you can use
Code:
mkt -o outdir join
to hash all files from the bin directory back to hashed form, and put it into the 'outdir' directory. Next add the binaries and you're ready to flash
Alternatively I included createpkg that will create a cab package from the OEM apckage found in the 'pkg' directory
Download and other stuff: http://winmo.sztupy.hu/manilakitchen.html
Sounds great! Downloading now. Thanks sztupy!
Yeah, good job sztupy, this will be a great addition.
nice...gotta buy a bigger house...so many kitchens
pcarvalho said:
nice...gotta buy a bigger house...so many kitchens :d
Click to expand...
Click to collapse
roflcopter
pcarvalho said:
nice...gotta buy a bigger house...so many kitchens
Click to expand...
Click to collapse
what you need is a microwave
sztupy said:
Missing functionality / bugs:
Embedded decompiled scripts can't be re-embedded into mode9 files automatically (this would need a command line mode9 editor
Click to expand...
Click to collapse
I can help you out with that. Not that it's already done but copying the relevant parts from m9editor together isnt the big deal.
6Fg8 said:
I can help you out with that. Not that it's already done but copying the relevant parts from m9editor together isnt the big deal.
Click to expand...
Click to collapse
I hoped so
unfortunately it's hard to tell a command line tool where to inject the scripts... An XML export/import function would be cool (export it to XML, without the binary scripts, then add the decomp'd scripts, and the importer would do its job esolving everything), but I know that won't be possible until you resolve the mode9 files completely...
sztupy said:
I hoped so
unfortunately it's hard to tell a command line tool where to inject the scripts... An XML export/import function would be cool (export it to XML, without the binary scripts, then add the decomp'd scripts, and the importer would do its job esolving everything), but I know that won't be possible until you resolve the mode9 files completely...
Click to expand...
Click to collapse
hm, didnt do much with xml, but i think i can figure that out. mode9 is almost done, there's only one bytegrave at the end of a mode9 file still unknown to me.
6Fg8 said:
hm, didnt do much with xml, but i think i can figure that out. mode9 is almost done, there's only one bytegrave at the end of a mode9 file still unknown to me.
Click to expand...
Click to collapse
your visualization of the m9 files look like xml, that's why I thought about that (but yaml could be a good serializator too). But this is just an idea, if you can tel me an easy way to tell a command line script where to inject a script that would be fine
And a command line CFC compressor is also needed
sztupy said:
your visualization of the m9 files look like xml, that's why I thought about that (but yaml could be a good serializator too). But this is just an idea, if you can tel me an easy way to tell a command line script where to inject a script that would be fine
And a command line CFC compressor is also needed
Click to expand...
Click to collapse
mode9 is basically binary XML, so i had no choice
The easiest way (at least for me) is byte positions just kidding ...
I'm on vacation next week, maybe i'll get struck by an ocean of light while skiing on one of the wonderful austrian mountains
CFC compressor .... I've that lying around somewhere here, shouldnt be a problem to adapt it.
an ambitious project... thank you
nice work great addition
Scripts update addon with the newest decompiled stuff.
Kitchen is now tested and considered BETA. Also added a great new tool: MKT to the kitchen. Read first post.
sztupy said:
Kitchen is now tested and considered BETA. Also added a great new tool: MKT to the kitchen. Read first post.
Click to expand...
Click to collapse
Just downloaded kitchen and getting ready to start playing. Just wondering, will this make a installable cab file for rhodium manila for touch pro? Of course with vga adapted files. I've noticed that previous attempts of making a cab for it have failed, but oem packages work when cooked in. I'm making a theme, which shouldn't require a full install, but would be nice to know.
showaco said:
Just downloaded kitchen and getting ready to start playing. Just wondering, will this make a installable cab file for rhodium manila for touch pro? Of course with vga adapted files. I've noticed that previous attempts of making a cab for it have failed, but oem packages work when cooked in. I'm making a theme, which shouldn't require a full install, but would be nice to know.
Click to expand...
Click to collapse
I tried to install it as a cab on NATF's ROM I'm using, and it worked flawlessly. It might break on a stock ROM though. The whole convert to cab thingy is alpha currently, but hopefully it will be solved.
sztupy, So how do you go about fixing the main function? I have the LUA file I've been working on done except for the main function and all the Q16.16 instances. But looking at the src.lua file, it appears chunks of the main are scattered throughout the file. Literally, I have code parts at the beginning of the file, in the middle and at the end of the file.
That's how the luadec output that you ran for me (because luadecguess was inaccurate) outputted the decompile.
So I'm stuck because I'm not sure how to proceed with fixing it. What do you do, just leave it where it's at and search for what it's referring to and fix it where you find it? Or do you cut/paste (move) it at the top of the src code in the order it's supposed to be in?
EDIT: never mind, left the code where it was and just searched out and fixed what it referenced. Other then the Q16.16 lines, everything is good.
Hi sztupy. Excellent work. Im poor and unemployed so although Id like to, I cant donate any cash at the moment. I like this project enough to offer body parts though, if any of yours fail
EDIT - bug report removed. was related to luaconv.exe. moving to another thread.
smotrs said:
sztupy, So how do you go about fixing the main function? I have the LUA file I've been working on done except for the main function and all the Q16.16 instances. But looking at the src.lua file, it appears chunks of the main are scattered throughout the file. Literally, I have code parts at the beginning of the file, in the middle and at the end of the file.
That's how the luadec output that you ran for me (because luadecguess was inaccurate) outputted the decompile.
So I'm stuck because I'm not sure how to proceed with fixing it. What do you do, just leave it where it's at and search for what it's referring to and fix it where you find it? Or do you cut/paste (move) it at the top of the src code in the order it's supposed to be in?
Click to expand...
Click to collapse
You can consider every function in the file as a value. It's just like a number or a string in this case, because in the main body you assign functions to some variables. So if you find something:
Code:
SomeStuff = function(foo)
lots of stuff
lots of stuff
lots of stuff
end
SomeOtherStuff = function(bar)
lots of stuff
lots of stuff
lots of stuff
end
Then in the main body this will translate to:
Code:
SomeStuff = funtion1
SomeOtherStuff = function2
And in the disassemlby to something like this:
Code:
R0 := Function(f1)
SomeStuff := R0
R0 := Function(f2)
SomeOtherStuff := R0
And of course the definitions of these functions will be put after the main body (just as with any other inlined function, the only exception is that compare/luadec and the other tools I made will handle these functions separately to ease decompiling). So if you have to fix the main body you have to only look at the part of the script which is not in a function...end body
Hi all!
I searched a lot on that topic an coocked loads of roms (for XPERIA/Kovsky/Venus) for testing purpose...But I cannot find a solution for that.
All my recently cooked ROMS (several Builds) are missing root certificates, I only have each two from HTC and Sony Ericsson in Setings. What went Wrong? where to find them? I thought to have found them in the following provxml's which actually is not the case I found out... (see below)
<old> Here is my problem. Build 23541 is seemingly (at least for me) missing root certificates. I managed to figure out they are included in a provxml called mxip_wpc_3.provxml. So I copied that one from a official LEO ROM (Build 21***) and did not change anything. After flash I can find it located in \Windows\ but the certificates are not appearing in Settings.
Now I now that provxmls need to be in UTF-8 format and set to read only, hidden and system. That ist tha case with this specific file. So what's wrong? </old>
I hope that someone can help me with that topic cause I have no other idea now.
Thanks A lot guys!
Hilaireg put together a really good tutorial om provxml's. Look it up, it may help. And make sure NET CF is cooked in (just a guess).
I guess you don't have that provxml added to any of dsm files . Just use this tool and add it to any of dsm files.
http://forum.xda-developers.com/showthread.php?t=523139
You can also use xml parser to check if file is good, for example Serna Editor.
tomcug said:
I guess you don't have that provxml added to any of dsm files . Just use this tool and add it to any of dsm files.
http://forum.xda-developers.com/showthread.php?t=523139
You can also use xml parser to check if file is good, for example Serna Editor.
Click to expand...
Click to collapse
Do you happen to know if that is needed too with platformrebuilder?
I've never worked with it but my guess is that you won't have to manually add provxml to dsm files.
Farmer Ted said:
Hilaireg put together a really good tutorial om provxml's. Look it up, it may help. And make sure NET CF is cooked in (just a guess).
Click to expand...
Click to collapse
Must be talking about this thread: http://forum.xda-developers.com/showthread.php?t=519548 Found it, thanks, very interesting indeed...this one will go into my bookmarks
Anyway, as i just copied the files from a working ROM I don not think something is wrong with them...
tomcug said:
I guess you don't have that provxml added to any of dsm files . Just use this tool and add it to any of dsm files.
http://forum.xda-developers.com/showthread.php?t=523139
You can also use xml parser to check if file is good, for example Serna Editor.
Click to expand...
Click to collapse
Thnkas as well, Layout is probably good, as the are woring in that LEO ROM.
I will look a bit deeper in your link, this sounds like the right way.
Are there other sugestions?
tomcug said:
I guess you don't have that provxml added to any of dsm files . Just use this tool and add it to any of dsm files.
http://forum.xda-developers.com/showthread.php?t=523139
You can also use xml parser to check if file is good, for example Serna Editor.
Click to expand...
Click to collapse
Tryed that now...But it did not help! Considering the xml is good (as it is working in a leo ROM) what else opportunities are there?
EDIT: Tried to import the provxml's (mxip_wpc_2.provxml and mxip_wpc_3.provxml) using AdvancedConfig but with no luck. Wondering...
Rename the file ZZZmxip_wpc_3.provxml and try again. EVK processes .provxml files in alphabetical order. If a directory referenced in the above .provxml is not created by a previously processed .provxml, then the modifications will not be applied.
I guess you are referring to this thread: http://forum.xda-developers.com/showthread.php?t=707717
From what I understand (probably very little) your provxml got executet too early as one shortcut was not yet present in the startmenu, so it stopped, right? With my files they do not depend on other files / reg values as these are just certificates...anyway, lets see
I will do so now, but I also tried to build a clean (no EXT) ROM from 23563 Rollup thread by Da_G and had the same problem! This is starting to get starnge...Will report in about 30 mins.
EDIT: Renaming did not help. Starting to get frustrated...
EDIT2: Even converting that provxml to a cab did not work. Am I looking in the wrong place?
Yes that thread, some ppl said that you need to edit the OEMs dsm where you add the provxml and add the provxml into it, dunno if it works... another one is... when a provxml fails in a corrupted line the next lines dont be executed but the before lines were set... so maybe the dirty way can works for you... if not works... your provxml is wrong in that thread many ppl said something about using a tool to see if the provxml is ok try them too
the dirty way to make it is... ad the provxml lines in your provxml to any other provxm... remember to keep the same attributes in that provxml.
+ Que PPC said:
Yes that thread, some ppl said that you need to edit the OEMs dsm where you add the provxml and add the provxml into it, dunno if it works... another one is... when a provxml fails in a corrupted line the next lines dont be executed but the before lines were set... so maybe the dirty way can works for you... if not works... your provxml is wrong in that thread many ppl said something about using a tool to see if the provxml is ok try them too
the dirty way to make it is... ad the provxml lines in your provxml to any other provxm... remember to keep the same attributes in that provxml.
Click to expand...
Click to collapse
trying the dirty way now.
I checked the provxml using a provxml2cab converter which usualy gives an error on bad files. And I am using Notepad++ which makes chacking quite easy. Than again, it comes from a official ROM and was not modified...
EDIT: Nope, not included!
what does that provxml has inside? some icons arrangement? or shortcuts?
Root certificates. both are attached below.
Are you using oskitchen alpha? There have been some problems with provxml not running (hence the alpha) but alpha5 should be fine.
Not sure? Its the NewUI Version and one of the last ones with the old folder structure (I think 1.27 or so)
derliebewolf said:
Not sure? Its the NewUI Version and one of the last ones with the old folder structure (I think 1.27 or so)
Click to expand...
Click to collapse
It was a problem specific only to the 1.31 alphas. Make sure the provxml files have the three attributes set (hidden, read-only and system), that could be the cause of the issue.
I am pretty sure the attributes are stet as you say.
If dirty way doesn't work, then I'm pretty sure it's something wrong with provxml file.
derliebewolf said:
I am pretty sure the attributes are stet as you say.
Click to expand...
Click to collapse
The only real way to find out is to set oskitchen to stop before imgfs generation or setting LZX and going quickly in the platformrebuilder temp\dump folder while it's generating IMGFS and using the ATTRIB command on the files in the dump folder to see what attributes those end up with. If all those three attributes aren't set the files won't run.
I'm pretty sure I've had provxml file with no attributes and it worked perfectly, but maybe I'm wrong .
The attached .provxml will not execute. It's supposed to associate icons with folders in the start menu, but it's just not working. It is totally unmodified from the Rhodium S2 ROM. The directories are there as the initflashfiles.dat file is unmodified and the folders are in the start menu. Anyone care to help?
Your file is fine so I guess that you have the same issue I had .
I guess you don't have that provxml added to any of dsm files . Just use this tool and add it to any of dsm files.
http://forum.xda-developers.com/showthread.php?t=523139
You can also use xml parser to check if file is good, for example Serna Editor.
Click to expand...
Click to collapse
Maybe I'm wrong, so if you already have this provxml added to any of dsm files, we'll look for more reasons. One more question, do you try to cook this into ROM or execute from Advanced Configuration Tool?
It's cooked in. The package is directly from the Rhodium S2 ROM, so I don't quite understand why it's not executing. I'm thinking about putting it in another OEM folder and seeing if that will help. Heck I'm lost, and about to turn it in for the night.
As I wrote, try adding it manually to dsm file in that OEM folder, this should help you, if this won't help, then I'm out of ideas.
Anyway, you can just add content of that provxml to another provxml, it's dirty way but probably the easiest one.
This happens because the messenger.lnk have not been created when this provxml is executed and it fails.
So just rename the provxml to mxipupdate_zprojectdefault_a_000.provxml
Notice the "z" ahead of the project.
This trick will put the provxml after the mxipupdate_windowsliveim_1.provxml, so the messenger.lnk will have been created and the provxml will run just fine.
But he said that provxml isn't excuted at all, I'm out of ideas . Anyway, it's worth to give your idea a try.
jwzg said:
The attached .provxml will not execute. It's supposed to associate icons with folders in the start menu, but it's just not working. It is totally unmodified from the Rhodium S2 ROM. The directories are there as the initflashfiles.dat file is unmodified and the folders are in the start menu. Anyone care to help?
Click to expand...
Click to collapse
the provxml isn´t executed on my rhodium as well. but renaming to mxipupdate_zzzzprojectdefault_a_000.provxml
does work for me.
as the posters above me wrote:
the problem seems to be the messenger package which includes another *provxml file which should be prozessed BEFORE mxipupdate_projectdefault_a_000.provxml but it isn´t! also *.provxml aren´t prozessed if there´s a failure inside. when you remove a program and you don´t clear the line in the *.provxml the file would not me prozessed.
this problem is related to platformrebuilder breaking something, you can pm airxtreme for info, it seems that he solved this problem in his wonderful kitchen
steph
Provxml can be launched but they stops at the line it find a problem so it seems that it doesnt works.
Platform rebuilder can reads DSM in EVK? or just in OsK? or none?
Renaming the .provxml solved the issue. Man, the start menu looks good now! Thanks!
Great, I wouldn't think about renaming on my own . Anyway, it seems that those provxml files are processed in alphabetical order, right?
everything is alphabetical order processed in platform rebuilder based kitchens ¬¬
Mod edit: Solved
Dude!!! The sameprob here with Leo ROM... same file... going to try your tip!
kurniawan77 said:
Dude!!! The sameprob here with Leo ROM... same file... going to try your tip!
Click to expand...
Click to collapse
@kurniawan77 - Did it work for you?
Same prob here, using osKitchen Zero for HTC LEO. Already tried renaming by adding zzz in name and also tried adding the provxml in dsm. Any other suggestions? This is drving me nuts, please help.
p/s: also tried opening the provxml in internet explorer/XML notepad 2007 - no errors. Made sure there are no "<?xml version="1.0" encoding="utf-8" ?>" in the headers.
Try to replace platformrebuilder.exe with another version, that did the trick for me.
Before you ask, sorry but I'm using a private edition of platformbuilder so I can't share.
I'm using platformrebuilder.exe v.2.1.0.0
tidus18 said:
@kurniawan77 - Did it work for you?
Same prob here, using osKitchen Zero for HTC LEO. Already tried renaming by adding zzz in name and also tried adding the provxml in dsm. Any other suggestions? This is drving me nuts, please help.
p/s: also tried opening the provxml in internet explorer/XML notepad 2007 - no errors. Made sure there are no "<?xml version="1.0" encoding="utf-8" ?>" in the headers.
Click to expand...
Click to collapse
tidus18 said:
@kurniawan77 - Did it work for you?
Same prob here, using osKitchen Zero for HTC LEO. Already tried renaming by adding zzz in name and also tried adding the provxml in dsm. Any other suggestions? This is drving me nuts, please help.
p/s: also tried opening the provxml in internet explorer/XML notepad 2007 - no errors. Made sure there are no "<?xml version="1.0" encoding="utf-8" ?>" in the headers.
Click to expand...
Click to collapse
You still have problems even with oskitchen 1.31beta3? Some people reported the new DSM-based provxml order to be working fine.
Evil Provxmls....
airxtreme said:
You still have problems even with oskitchen 1.31beta3? Some people reported the new DSM-based provxml order to be working fine.
Click to expand...
Click to collapse
Hi Airxtreme - Thanks for developing the kitchen! Its really great. But i just recently moved to osK Zero from ervius. Previously in ervius i didnt even bother to add provxmls in any dsm. I dont quite understand DSM management fully, but i did add the provxmls in DSM of my ext package (ext package contains my custom icons for start menu and the provxml to add reg entries).
When i get back home, i will try to rebuild the ROM with older version of kitchen and report back. Currently im using v1.31Beta3.
p/s: i had trouble with theme provxmls as well, finally i had to put all the theme files in Operatorpkg, and put the xml entries in HTC's provxmls (the one named HTC_100) for it to work.
Laurentius26 said:
Try to replace platformrebuilder.exe with another version, that did the trick for me.
Before you ask, sorry but I'm using a private edition of platformbuilder so I can't share.
I'm using platformrebuilder.exe v.2.1.0.0
Click to expand...
Click to collapse
2.1.0.0? Then what's the version that is publically available? And can you say something about the new functions, etc.? Thanks!
tidus18 said:
Hi Airxtreme - Thanks for developing the kitchen! Its really great. But i just recently moved to osK Zero from ervius. Previously in ervius i didnt even bother to add provxmls in any dsm. I dont quite understand DSM management fully, but i did add the provxmls in DSM of my ext package (ext package contains my custom icons for start menu and the provxml to add reg entries).
When i get back home, i will try to rebuild the ROM with older version of kitchen and report back. Currently im using v1.31Beta3.
p/s: i had trouble with theme provxmls as well, finally i had to put all the theme files in Operatorpkg, and put the xml entries in HTC's provxmls (the one named HTC_100) for it to work.
Click to expand...
Click to collapse
Those having problem with provxmls where it is used to overwrite other provxmls in sys (ie: for theme settings), please try this http://forum.xda-developers.com/showpost.php?p=7038082&postcount=2477
This version of your kitchen solved all my probs. THANKS!!!!!!!!!!!!
I only tried to help make the provxml load
Bepe created the kitchen tool and knows everything about it.
Edit; a bit late but the version I use is 2.1.0.0 indeed.
cnzqy1 said:
2.1.0.0? Then what's the version that is publically available? And can you say something about the new functions, etc.? Thanks!
Click to expand...
Click to collapse
tidus18 said:
Those having problem with provxmls where it is used to overwrite other provxmls in sys (ie: for theme settings), please try this http://forum.xda-developers.com/showpost.php?p=7038082&postcount=2477
This version of your kitchen solved all my probs. THANKS!!!!!!!!!!!!
Click to expand...
Click to collapse
glad it worked out for u... been away for days... working on bugfixes... and more. v1.31b3 from worked out even better... sorry for late response