I own an Xperia X1i.
Lets take a stock module from OEMDrivers folder such as Animation.dll.
It contains these files: Animation.dll S000, S001, S002, S003, imageinfo.txt, imageinfo.bin.
Lets now take a module that i have created from an dll file such as Audio_Decoder_Api.dll.
It contains S000, S001, S002, S003, imageinfo.txt, imageinfo_pe.txt, imageinfo.bin.
It doesn't contain Audio_Decoder_Api.dll as a file in it.
I noticed that modules from OS don't contain *.dll either.
Why is that?
Should i convert old modules to files and back to module to have the same structure for all?
Or the is no gain in that?
I think what happened is that when you dumped the stock rom, it recmodded the modules, and that's why you have the dll file in the module. I'm not sure why it happens, but it's happened to me before as well.
OK, thanks. I will ->refile->remodule again on my own then.
Farmer Ted said:
I think what happened is that when you dumped the stock rom, it recmodded the modules, and that's why you have the dll file in the module. I'm not sure why it happens, but it's happened to me before as well.
Click to expand...
Click to collapse
It happens when you dump with Ervius' Visual Kitchen, because of the recmod.exe file in the Tools>IMGFS folder. If you delete or change the name of that file, you won't get this when you dump. Or just clean the dump with the dump sorter.
Related
I'm trying to graft the OEM folders from one ROM to another. However, I cannot copy the files from the ROM on the device because they are protected. The directories will not compile themselves when the new ROM is flashed because they are from a different ROM. I know this has been done. The question is how?
Hmm are you trying to copy files from the device to a folder? or simply replace modules from another release?
To fix modules into working DLLs/EXEs simply use recmod
e.g
recmod CameraDriver.dll
It will then recreate CameraDriver.dll inside the CameraDriver.dll folder with the IAT table all fixed.
Hope this is what you meant
delete the original folder or the file that you want to replace with the new one, or remove it to another folder if you want to keep it as a back up
I can see you need to replace module (folder) with file or file with module?
is that what you want
I've used the method described by whiterat. Thanks!
ok, but when you dump the ROM, it will make the Recompiling file automaticly, at least with me
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.
hi,
i have modified bepe's new rom kitchen (PRB) to suit my needs.
for months it's working flawlessly.
due to some updated rom tools, i have modified the kitchen batch to include the updated tools. i have updated all the folders in the kitchen (EXT, OEM, ROM, SYS, tools & toolset) with the latest packages, tools, etc.
then 2 weeks ago, i can't build a rom with my kitchen.
everytime prb executes, it is showing this platformrebuilder errorlevel: -1073740777.
today, i have managed to trim down the cause for this error.
if i have a module inside EXT folder, (i.e. EXT\COMMON\Scrolling\files\PhysicsEngine.dll - which is a module), prb throws the error.
however, if i move the module outside the files folder, (i.e. EXT\COMMON\Scrolling\PhysicsEngine.dll), or recmod the module (convert the module to file), there is no error. i can build a rom with success.
i have this packages with module before i modified my kitchen and i can build without error.
i would like to ask if you have also encountered the same error, or its just me and i would also like to know what could be the cause for the error.
thanks very much.
regards,
mike
Its trying to replace the module, and couldnt since its a module. Want to use the the one in EXT, then you will have to delete the one in OEM or SYS.
Yeah, I'm agree. I has a Mui file as a module (???) in an Oem_lang folder. This cause the error. I just change the module for a mui file and all goes ok.
thanks for the replies guys.
regards,
mike
I recall seeing that issue with certain versions of EVK. I also recall, ervius stating that he had fixed EVK to support both locations for modules:
.\packagename\<modulefile.ext>
.\packagename\files\<modulefile.ext>
A search through the EVK thread should bring up the particulars. Search using the internal search function by member name - his or mine (think it was me that brought it to his attention). Also, the module folder only needs to contain the imageinfo.* & S#### files - the .DLL/.EXE/.MUI/etc. file doesn't need to be present ... it will get created a build time.
HTH,
* EDIT *
http://forum.xda-developers.com/showthread.php?p=4243721#post4243721
hi,
after further investigation, i have found out that if the original module's attribute is not the same as the new module (i.e. PhysicsEngine.dll\imageinfo.*, S00x, etc.), prb will throw the error -1073740777. otherwise, no problem/error encountered.
so my conclusion is, if you have to overwrite a module, the new module should have the same attributes as the old module.
regards,
mike
twisted said:
hi,
after further investigation, i have found out that if the original module's attribute is not the same as the new module (i.e. PhysicsEngine.dll\imageinfo.*, S00x, etc.), prb will throw the error -1073740777. otherwise, no problem/error encountered.
so my conclusion is, if you have to overwrite a module, the new module should have the same attributes as the old module.
regards,
mike
Click to expand...
Click to collapse
So how do we correct the attribute?
ai6908 said:
So how do we correct the attribute?
Click to expand...
Click to collapse
i've done it manually, right-click the original file (i.e. S000) and check the attributes, should be the same with the new file (i.e. if original file S000 has attribute set to Hidden Read-only, the new file S000 should also be set to Hidden Read-only).
regards,
mike
Hi.
Going to thread:
I build my own kitchen which uses platform rebuilder (far called PRB), it's for Universal and contain 21884 build (my favourite ).
Everything goes okay, registry, modules, files is okay but the problem is known .provxml issue.
I use PRB 2.1 (displays mmap)
All provxml and dsm are readonly, system and hidden
I tried to put all provxml to external dsm, also add all files into one dsm, updating existing dsm, renaming provxml's to mxip_zzzz << you know the 'zzzz' makes it process at last.
No success.
Fail effect is:
No Office (which installs via provxml), no start menu icons, no theme loaded, classicblue failed. etc.
Any ideas?
bump, without any ideas?
try to leave the Hidden attribute.
FDCTask Manager (aka DotFRED) can import *.*XML file; it's handy for testing and ensuring that the XML file is properly formed. Have a look at this post and the reference link at the end:
http://forum.xda-developers.com/showpost.php?p=5959794&postcount=9
It is an issue with setting the attributes correct when building OS.
http://www.mobileunderground.info/showthread.php?t=17128&p=45430#post45430
ai6908 said:
It is an issue with setting the attributes correct when building OS.
http://www.mobileunderground.info/showthread.php?t=17128&p=45430#post45430
Click to expand...
Click to collapse
No way, it didn't helped and didn't fixed anything.
My kitchen main bat file looks that now:
http://pastebin.com/ac1rtNeV
Any ideas for now? Maybe about DSMes?
EDIT:
Seems to be fixed
Helped another attrib config, take a look on my kitchen. Closing
http://pastebin.com/J9RrGmj8
I need compressed xip.bin files to cook a rom. I have unzipped xip files but I dont know how to make it a "bin" file. If I can find a randomize xip file for my working sys, I can port it with xip_kitchen for my device. Please help me about it. I just need a bin file. Thanks..
Read here and here.
burakgon said:
I need compressed xip.bin files to cook a rom. I have unzipped xip files but I dont know how to make it a "bin" file. If I can find a randomize xip file for my working sys, I can port it with xip_kitchen for my device. Please help me about it. I just need a bin file. Thanks..
Click to expand...
Click to collapse
I posted the utility a year ago. Not too much to read
http://forum.xda-developers.com/showthread.php?p=5142343#post5142343
It generates bin file from MSXIPKernel
You guys rock. Thanks!