Database Users

Can't access system dlls

Hi,
First of all sorry for double posting.
I'd already posted in the universal forum, but then I figured this also concerns other modules
So here goes:
I'm trying to disassemble the Camera app with IDA, it wants to see some DLLs like note_prj.dll and mfcce300.dll, but when I try to copy them from my Universal I get an access denied error :/
Is there any other way to get these files ?
Thanks,
TB

TheBlasphemer said:
Hi,
First of all sorry for double posting.
I'd already posted in the universal forum, but then I figured this also concerns other modules
So here goes:
I'm trying to disassemble the Camera app with IDA, it wants to see some DLLs like note_prj.dll and mfcce300.dll, but when I try to copy them from my Universal I get an access denied error :/
Is there any other way to get these files ?
Thanks,
TB
Click to expand...
Click to collapse
They are XIP and that is why you cannot copy them - they are not normal files. There are several ways to dump such modules.
1. Use my TestWM5 tool (search forum). It would produce incorrectly dumped files with garbage at data sections, at the end of file and all sections merged to one, but IDA can understand such modules
2. Use rdmsflsh.pl by itsme. It would produce better files, but as far as I remember it is incompatible with universal ROM
3. Use my viewimgfs tool, but in this case you have to manually reconstruct a DLL from individually dumped sections.

Cooking SDKCERT in ROM

Hallo everybody,
I just want to ask how I can built in SDKCERT directly into ROM.If I want to convert SDKCERT.CAB to EXT then after I have again CAB so newerending story.

You won't need to use the SDKCERT package. If you are using Ervius Visual Kitchen for example, all you need to do is ensure that Disable Cert(ificate) checking is selected. This way, your compiled ROM will already have Certificate checking disabled allowing you to install updated drivers and such.
This tutorial discusses some of the changes you'll likely need to make:
http://forum.xda-developers.com/showthread.php?t=526610
HTH,

if you still need it ,here its is. just add to any package.

faria said:
if you still need it ,here its is. just add to any package.
Click to expand...
Click to collapse
Thank you very much!!!

Johan Kraczmar said:
Thank you very much!!!
Click to expand...
Click to collapse
Np.
Here is a little tip for future...
most certificates are in cab form,open the cab with winrar,you will see a file called;_setup.xml, that is the cert info.
just rename _setup.xml to mxip_999_certname.provxml and you done.

faria said:
if you still need it ,here its is. just add to any package.
Click to expand...
Click to collapse
Did I understand correctly that I would need to add this to each package that needs a certificate?
Thanks

He said that you need to add this in every cab that need certificates, if you use EVK or Oskitchen you dont need anything because they auto patch the certs.
Lewy1 said:
Did I understand correctly that I would need to add this to each package that needs a certificate?
Thanks
Click to expand...
Click to collapse

af974 said:
He said that you need to add this in every cab that need certificates, if you use EVK or Oskitchen you dont need anything because they auto patch the certs.
Click to expand...
Click to collapse
Thanks. The problem is that I've tried quite a few times to install the Vogue Camera as an EXT with EVK, and I always end up with the "The file 'camera' cannot be opened. Either is not signed with a trusted certificate or one of it's components cannot be found." etc.

Did you tried the solution in post #3?
For which device are you trying to install?...from Vogue to -> ?
Sometimes from different devices isnt a certificate fault but some missing dll.
Check for this app Dependency walker and search if you have all the modules to make run camera Vogue.
Lewy1 said:
Thanks. The problem is that I've tried quite a few times to install the Vogue Camera as an EXT with EVK, and I always end up with the "The file 'camera' cannot be opened. Either is not signed with a trusted certificate or one of it's components cannot be found." etc.
Click to expand...
Click to collapse

Lewy1 said:
Thanks. The problem is that I've tried quite a few times to install the Vogue Camera as an EXT with EVK, and I always end up with the "The file 'camera' cannot be opened. Either is not signed with a trusted certificate or one of it's components cannot be found." etc.
Click to expand...
Click to collapse
Hi Lewy1,
You are missing a package dependency. If you navigate to the .\Windows folder using File Explorer on your device and try and launch the Camera application, you will encounter an error - confirming that you have dependency issue.
Have a look at this post:
http://forum.xda-developers.com/showpost.php?p=4259031&postcount=1070
HTH,

Lewy1 said:
Thanks. The problem is that I've tried quite a few times to install the Vogue Camera as an EXT with EVK, and I always end up with the "The file 'camera' cannot be opened. Either is not signed with a trusted certificate or one of it's components cannot be found." etc.
Click to expand...
Click to collapse
Yeah, that is just a generic error message, and it almost never has anything to do with certs. You could be missing dependencies, or it could just be that you have a broken shortcut. One of the problems with the 6.5 start menu is that you can't always tell just by looking that the shortcut is effed, because you may have an ico assigned through the registry. Use Total Commander to see if you have the correct shortcut path.

hilaireg said:
Hi Lewy1,
You are missing a package dependency. If you navigate to the .\Windows folder using File Explorer on your device and try and launch the Camera application, you will encounter an error - confirming that you have dependency issue.
Have a look at this post:
http://forum.xda-developers.com/showpost.php?p=4259031&postcount=1070
HTH,
Click to expand...
Click to collapse
Farmer Ted said:
Yeah, that is just a generic error message, and it almost never has anything to do with certs. You could be missing dependencies, or it could just be that you have a broken shortcut. One of the problems with the 6.5 start menu is that you can't always tell just by looking that the shortcut is effed, because you may have an ico assigned through the registry. Use Total Commander to see if you have the correct shortcut path.
Click to expand...
Click to collapse
First of all, thanks guys for your help!
Yes, your right that the problem is also when I try launching the camera from the windows directory. Now the problem is that I don't understand too much when it comes to digging into the contents of these files, so I think I'll need some help.
I assumed I needed Dependency Walker which you wrote about in your Kitchen Utensils review, so I opened the camera.exe and the results are attached as a Dependency Walker Image. The camera EXT I have come from converting a cab that's been floating around XDA. By the way I had the same problem when using the mega camera.
Thanks so much for the patience and help.

Had a look at the .DWI file you attached. Your next steps:
Create a folder on your system (ex: C:\WINMO_OS)
Copy all of the camera package files to the folder.
In DEPENDS, remove all of the "Module Search Order" paths - Options menu.
Add the folder path (ex: C:\WINMO_OS)
Search your kitchen for each file that is listed in CAMERA.EXE and copy them to the folder.
Once you have the files from CAMERA.EXE in the folder, open each of the yellow ( ? ) files.
Repeat the steps above until you have examined all of the files in the folder you created.
Essentially, you want to locate all of the files listed in each .DLL, .EXE, etc. that is displayed in DEPENDS.
If the files appear in the .\SYS or .\OEM folder, it's likely those aren't the issue. Some files may be modules; it's likely those aren't the issue as well - I usually RECMOD a copy of the file and place it in the folder or I copy it from the device when connected using USB. This will reveal additional files that are "missing". I suspect you will discover the missing dependency to be in another file. If you find the files in packages, it's likely the entire package is a dependency. If you can't find a file, make note of it and continue on. At the end, post the list of files you couldn't find.
Lastly, examine each of the .REG files for references to other files; you may need to do a global search through the kitchen to find other packages that may be writing to the same keys ... these will likely be dependant packages as well.
HTH,
* EDIT *
If at all possible, it would be beneficial for you to find the official source ROM that the package originated from.

hilaireg said:
Had a look at the .DWI file you attached. Your next steps:
Create a folder on your system (ex: C:\WINMO_OS)
Copy all of the camera package files to the folder.
In DEPENDS, remove all of the "Module Search Order" paths - Options menu.
Add the folder path (ex: C:\WINMO_OS)
Search your kitchen for each file that is listed in CAMERA.EXE and copy them to the folder.
Once you have the files from CAMERA.EXE in the folder, open each of the yellow ( ? ) files.
Repeat the steps above until you have examined all of the files in the folder you created.
Essentially, you want to locate all of the files listed in each .DLL, .EXE, etc. that is displayed in DEPENDS.
If the files appear in the .\SYS or .\OEM folder, it's likely those aren't the issue. Some files may be modules; it's likely those aren't the issue as well - I usually RECMOD a copy of the file and place it in the folder or I copy it from the device when connected using USB. This will reveal additional files that are "missing". I suspect you will discover the missing dependency to be in another file. If you find the files in packages, it's likely the entire package is a dependency. If you can't find a file, make note of it and continue on. At the end, post the list of files you couldn't find.
Lastly, examine each of the .REG files for references to other files; you may need to do a global search through the kitchen to find other packages that may be writing to the same keys ... these will likely be dependant packages as well.
HTH,
* EDIT *
If at all possible, it would be beneficial for you to find the official source ROM that the package originated from.
Click to expand...
Click to collapse
Thanks, that was quick. Looks like I got a lot of work ahead of me.

[SOLVED] platformrebuilder errorlevel: -1073740777

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

[Q]How to create XIP driver

Hi.
I am just working on my own driver. I tested its body and seems to be ok but I have some problems concerned with the fact, system does not want to load it at boot time. Fortunately I can load it further having already access to the shell so I know it works as it should.
I suspect that maybe it is caused driver is not XIP'ed becuase it has been created as single dll file. Maybe my driver .dll file should be inserted in kitchen as module for example in mydriver.dll directory and I have to place in this directory needed Sxxx files and imageinfo files like other available drivers have ? Am I right ?
Regards
fxdjacentyfxd

You may want to pm Shadrac; he's the author of Extendir, which is a xip file system driver. I think most people use it as a file and not a module.

Farmer Ted said:
You may want to pm Shadrac; he's the author of Extendir, which is a xip file system driver. I think most people use it as a file and not a module.
Click to expand...
Click to collapse
Thanks for info.
Regards
fxdjacentyfxd

[SOLVED]First boot customization doesn't start

Hi,
I'm using the latest osKitchen (v1.33.5) to build my own ROM for the HTC Kovsky (SE Xperia X1). Followed the tutorial, imported the latest official R3A WWE build, added a WM 21916 build and started cooking. But there's no first boot customization after a flash/hard reset. There are no errors, executing AutoRun.exe from the Windows folder doesn't seem to work either.
The config.txt (used by AutoRun and RunCC) files are left stock, but editing them doesn't make a difference. How can I fix this? If you need more information, just ask. I'll reply asap.

Have you added the runcc.lua file and redirected it to the right config.txt?
If so, flash the ROM and look whether those files are in \Windows\ (and just not executed) or not present.

Flashed the ROM: runcc.lua was already added and it redirects to the right config.txt. Paths are correct.

...
this happened to me not so long ago:
check that the autorun.exe and config**.txt files do not get overwrote during rom creation.
check that there are no duplicate files with those file names..
good luck!
Rn

I don't think those files are being overwritten during ROM creation. How can I check this? Can't find the Autorun.exe in the kitchen but after building and flashing it is visible in the Windows folder on the device. There are no duplicate files, triple checked that.
Tried building a new kitchen from scratch, an untouched build (only importing the stock ROM and the 21916 build) didn't have a first boot customization either.

I remember figuring this out on my X1 a year ago was a pain in the a*s. Can't recall where the problem was anyway. I could upload my OEM Packages for you if you'd like to? I'm using a older version of that kitchen anyway so this "could" lead to new problems...

That would be great! Please let me know what kitchen version you used, if there are any problems I can try to roll back to that one.

I PM'd you. Most persons would not know what to do with said files so it makes no sense posting them here I guess...

...
hey dude,
not sure what your problem is if all your config**.txt are there and there is no duplicate files, for me i had a mortscript called "autorun.exe" which obviously overwrote my original autorun.exe and caused my device to do no customisation.
erm, as for not finding your autorun.exe
lots of files in the kitchen are hidden and the windows hidden files toggle does not show all the hidden files for some reason :/
me personally i use ACDSee photo manager 9 to view the files in my kitchen, i then select all the files and untick the 'hidden' properties.
ALL the files you couldnt see in windows explorer are always visable using Acdsee, by unticking the properties with Acdsee, it now makes them visable in windows explorer.
hope you understand what i meen :s
btw, i only use acdsee9 to view my pictures and to change the properties of the files.
i edit all my images with photoshop and paint.
Rn

derliebewolf said:
Most persons would not know what to do with said files so it makes no sense posting them here I guess...
Click to expand...
Click to collapse
According to my searching results this issue seems to be very rare. Posting the download link here shouldn't harm others.
For osKitchen version number you mentioned in your PM, open the kitchen and use Help -> About. Don't know if this option was present in earlier builds, but at least in 1.33.5 it is.
raving_nanza said:
erm, as for not finding your autorun.exe
lots of files in the kitchen are hidden and the windows hidden files toggle does not show all the hidden files for some reason :/
Click to expand...
Click to collapse
I wasn't at the stage of using Mortscript in my ROMs yet. Untoggle hidden system files in Windows folder options did the trick, I found AutoRun.exe
Now I'm gonna sit and wait until the download is available...

DillonDarko said:
I wasn't at the stage of using Mortscript in my ROMs yet.
Click to expand...
Click to collapse
let me know when you are at that stage dude, ive got a small collection of usefull scripts that might prove themselves usefull.
DillonDarko said:
Untoggle hidden system files in Windows folder options did the trick, I found AutoRun.exe
Click to expand...
Click to collapse
cool man, but remember:
the windows hidden files toggle does not show all the hidden files.
Acdsee will show them all so none are hidden, trust me
Rn

NVM....thought of a some other problem...

raving_nanza said:
let me know when you are at that stage dude, ive got a small collection of usefull scripts that might prove themselves usefull.
Click to expand...
Click to collapse
Will do.
For the others that might experience this problem, the download link for EXT and OEM packages available here. These packages are untested, but I'm cooking them now. Thanks for the help. Scroll down for the fix.

So I think it's working now?
@All: please be aware, those packages are device-specific and for HTC Kovsky / SE Xperia X1!

Ok, tried replacing the existing packages with those from derliebewolf. Even when left untouched or using different (correct) commands there's still no customization. @derliebewolf, could you upload your "osKitchen.exe" and "Resources" directory for me? It's all I need, I can fill the kitchen from scratch there.
If this turns out to be a kitchen specific problem I won't hesitate posting it in the official osKitchen thread.

This is a pretty complicated problem to give advise.
Just a suggestion, didn't you modified/removed something from your initflashfiles.dat?
I mean the startup.
Compair it with a stock rom if you did and check if something is missing.
On my HD2:
Directory("\Windows\StartUp"):-File("ConfigureDevice.lnk","\Windows\ConfigureDevice.lnk")
Directory("\Windows\StartUp"):-File("bugtrap.lnk","\Windows\bugtrap.lnk")
Directory("\Windows\StartUp"):-File("HTCStartUp.lnk","\Windows\HTCStartUp.lnk")
Directory("\Windows\StartUp"):-File("PKG.lnk","\Windows\PKG.lnk")
Directory("\Windows\StartUp"):-File("SignatureReplace.lnk","\Windows\SignatureReplace.lnk")
Directory("\Windows\StartUp"):-File("Welcome.lnk","\Windows\welcome.lnk")
Click to expand...
Click to collapse
You tried everything possible so I taught maybe this could be possible.
On Xperia it's probably about the same.
DillonDarko said:
Ok, tried replacing the existing packages with those from derliebewolf. Even when left untouched or using different (correct) commands there's still no customization. @derliebewolf, could you upload your "osKitchen.exe" and "Resources" directory for me? It's all I need, I can fill the kitchen from scratch there.
If this turns out to be a kitchen specific problem I won't hesitate posting it in the official osKitchen thread.
Click to expand...
Click to collapse

You really need to leave the welcome.lnk line in there, or else you won't get the alignment screen and you can't boot the device up.

Found the issue: an incomplete initflashfiles.dat. By adding the lines below to a stock initflashfiles.dat the whole issue has been fixed.
Code:
Directory("\Windows\StartUp"):-File("CheckAutoRun.lnk","\Windows\CheckAutoRun.lnk")
Directory("\Windows\StartUp"):-File("AutoShortcut.lnk","\Windows\AutoShortcut.lnk")
Turned out a stock initflashfiles.dat file doesn't have those lines included by default. Thanks to all for the help, expect a new custom Xperia X1 ROM soon.

That's nice to hear, congrats.
Please at [SOLVED] to the topic title and I will link this thread to the solved cases sticky.
DillonDarko said:
Found the issue: an incomplete initflashfiles.dat. By adding the lines below to a stock initflashfiles.dat the whole issue has been fixed.
Code:
Directory("\Windows\StartUp"):-File("CheckAutoRun.lnk","\Windows\CheckAutoRun.lnk")
Directory("\Windows\StartUp"):-File("AutoShortcut.lnk","\Windows\AutoShortcut.lnk")
Turned out a stock initflashfiles.dat file doesn't have those lines included by default. Thanks to all for the help, expect a new custom Xperia X1 ROM soon.
Click to expand...
Click to collapse

DillonDarko said:
Found the issue: an incomplete initflashfiles.dat. By adding the lines below to a stock initflashfiles.dat the whole issue has been fixed.
Turned out a stock initflashfiles.dat file doesn't have those lines included by default. Thanks to all for the help, expect a new custom Xperia X1 ROM soon.
Click to expand...
Click to collapse
Which makes me woder whether those lines are missing in my initflashfiles.dat as well? RunCC is working perfectly anyway... Glad you solved it!