Related
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.
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
I've been reading up on cooking ROM's and with the help of leeston i managed to create a basic ROM earlier in the week. After searching for guides / tutorials on this stuff im really not that much the wiser, i cant seem to find anything that explains it well enough, there always missing details. The actual cooking process seems fairly straightforward but its those extra bits im missing ie
how do i add my own packages - am i right in just copying them to the SYS folder or is there more to it ?
how do i edit the registry - I know how to edit the registry once the ROM is loaded onto my phone but how do i do it from the ROM without the phone ?
how do i add things to the start menu - When i add packages to the SYS folder and load the ROM into my phone the shortcuts dont seem to be in my start menu
how do i add sense - i've loaded the packages but it never starts and theres no sense option in today settings
im new to this so as you'd imagine the questions i have are endless ...
Im sure most of this info is on XDA already somewhere but i just cant find it, maybe im searching for the wrong term or something.
Any help from the chef's would be great, perhaps you could provide links to tutorials / info you've used when learning to cook. Im sure this stuff would be useful to everyone and may even encourage more to have a go at cooking .
drkdeath5000 said:
1.how do i add my own packages - am i right in just copying them to the SYS folder or is there more to it ?
2.how do i edit the registry - I know how to edit the registry once the ROM is loaded onto my phone but how do i do it from the ROM without the phone ?
3.how do i add things to the start menu - When i add packages to the SYS folder and load the ROM into my phone the shortcuts dont seem to be in my start menu
4.how do i add sense - i've loaded the packages but it never starts and theres no sense option in today settings
.
Click to expand...
Click to collapse
I am still new to cooking but I'll tell you what i believe to be correct.
1.Yes. To add a package to a rom you put the package into the SYS folder.
However be aware that the kitchen used for the TG01 cannot handle EXT (visual) packages, only OEM (old) packages can be used. Use Totalfires package converter to convert between the 2 types.
The above info is not strictly true but is what you need to know when cooking for the TG and i don't have the time or knowledge to write a complete tutorial.
2. Editing the registry is all to do with .RGU files, you can create a package with a new one in or edit the existing ones within the packages in the SYS folder. You can edit them with notepad but i suggest using Notepad2.
Once you open an .RGU file you should recognize the reg key text in the file and edit it accordingly. As far as i am aware the file MUST have REGEDIT4 in the first line and an empty line at the bottom in order to work. Another way is to edit the regkey on your device then export the regkey using resco or something similar, then rename the resulting file from .reg to .rgu then open it in note pad and copy and paste it into another packages .rgu file, or create a custom package for that .rgu file.
The registry can also be modified using cab files during autorun, but this can be a little messy as the cab can be uninstalled by the end user causing problems.
3. To do this you need to edit the initflashs.txt file within the . This can be done manually or with one of the many package tools available on this site. The one i use is below, it does the hardwork for you, you click a few options and it edits the required files as needed.
4. Sense is a funny one. You should just need to add all the required packages to the SYS folder and away it goes. Unfortunately this is rarely the case. It should just a case of making sure all the sense packages are there, including its many dependencies. Sense is one of my weaker areas so maybe some one else has better advice.
Hope this is useful.
do you have a loooong far way, but read the forumposts an try, try and shortPin and try. that was my way, or is my way. i have don´t helping, all found with google and in xda forum.
unfortunately, my English knowledge is terrible. otherwise I would write more.
best to dump a officiels ROM or miROM5 , then you have an example
related post here
http://forum.xda-developers.com/showthread.php?t=750261
PC Software Reg-editor
http://ceregeditor.mdsoft.pl/index.php?id=1〈=en
CAB to OEM
http://forum.xda-developers.com/showpost.php?p=3942000&postcount=1
EXT to OEM
http://www.ppckitchen.org/forums/re...e666.ppckitchen.org/Tools/EXT%20to%20PPCk.exe
All folder to cooking need a .dsm (and/or) .rgu file
RGU name Generator (such as Reg- file) , dsm become automatically
http://www.famkruithof.net/uuid/uuidgen (Fetch UUIDs of another type to Version 4)
do you have a loooong far way!
... Or make a good donation to nokser or ffboy, they teach you
Hi my friend, I have a problem to cook a ROM with cab which required a reboot or witch have a information message ( SWYPE or GPSMOdDriver for example)
Do you know a solution for this please?
Thanks in advance.
Thanks for the info leeston and miro ;-). I havent had time to try it yet but will be over weekend and im almost sure now i know where to find the registry files ill be able to cook something decent up since that was my main problem. Thanks again for the help.
EVEALEX62 said:
Hi my friend, I have a problem to cook a ROM with cab which required a reboot or witch have a information message ( SWYPE or GPSMOdDriver for example)
Do you know a solution for this please?
Thanks in advance.
Click to expand...
Click to collapse
I may be wrong but when the cab files are first installed doesnt it automatically reboot ? If not you can always do a manual reboot ;-).
I've tried everything to get sense working but im just having no luck ... copied the packages to the sys folder, flashes fine, boots fine but no sense and now theres no setting shortcut in the start menu ?
Could i ask for the exact procedure for installing sense please ? Im getting my packages from here but replacing the 2017 home with 2016. Could i perhaps be missing something ?
Thanks again
drkdeath5000 said:
I may be wrong but when the cab files are first installed doesnt it automatically reboot ? If not you can always do a manual reboot ;-).
Click to expand...
Click to collapse
I have try to delete the line "Reboot" after autocabinstall but nothing change the phone always reboot ... I think the only thing is to do OEM package...
I have test with many cabs but nothing works same as you with Sense ...
Have you found solutions ?
EVEALEX62 said:
Hi my friend, I have a problem to cook a ROM with cab which required a reboot or witch have a information message ( SWYPE or GPSMOdDriver for example)
Do you know a solution for this please?
Thanks in advance.
Click to expand...
Click to collapse
The solutoin is to use autorun instead of cabinstl, you can then write a custom script to handle the input required by the cab.
However this is above my head, and i couldn't get autorun to work. FFBOY knows how but i doubt you will get his help as he doesn't seem to check any threads other than his own rom threads, and if he does his responces are few and far between.
drkdeath5000 said:
I've tried everything to get sense working but im just having no luck ... copied the packages to the sys folder, flashes fine, boots fine but no sense and now theres no setting shortcut in the start menu ?
Could i ask for the exact procedure for installing sense please ? Im getting my packages from here but replacing the 2017 home with 2016. Could i perhaps be missing something ?
Thanks again
Click to expand...
Click to collapse
Those are the packages i used and they work so it's not the packages, but i cheated and dumped a sense rom then modified it. I don't have time to try and work out how to do it properly unfortunatley.
leeston2379 said:
Those are the packages i used and they work so it's not the packages, but i cheated and dumped a sense rom then modified it. I don't have time to try and work out how to do it properly unfortunatley.
Click to expand...
Click to collapse
Well atleast i know the packages are fine, i was starting to wonder if that was the problem . Theres some satisfaction in doing it yourself but like miro said i think its just too much for me, ill give it another go later in the week and if that fails ill just dump a sense rom like you did ... if there was just a tutorial on installing sense packages etc id be fine, with sense being so popular you'd think there to be loads of tuts.
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!
hi again guys.i have THIS OEM Apps folder,and i want to leave only the HTC Camera in it...i'ved tryed 4-5 times.flashed the rom but i still get CAmera.exe is not found or bla bla...doesnt have a trusted certificat...someone can help me extract it pls? just tell me what to delete and what not
I thinking that you either dont have netcf or your shortcut (lnk) is pointing to the wrong file.
ai6908 said:
I thinking that you either dont have netcf or your shortcut (lnk) is pointing to the wrong file.
Click to expand...
Click to collapse
hmm,how do i edit shorcuts is SYS?
PS: i don't think the shortcut is the problem,and i have NETCF
The shortcut's probably bad, although I'm not really sure what the issue is based on the first post. You need to be more clear what the issue is. When do you get the error? What exactly did you do, or are you trying to do? No one can possibly know after reading the first post, we can only guess.
Just edit the shortcut with total commander on your device, or use notepad2 or something similar on your pc. Editting shortcuts is an important skill for cooking. That error occurs anytime you try to launch a program using a bad shortcut.
i'ved managed to extract the camera from the OEM folder,now works,but if i want to delete the picture the Camera crashes...
PS: now i'm trying again to set the camera as an EXT package...and change the shourtcut
Farmer Ted said:
The shortcut's probably bad, although I'm not really sure what the issue is based on the first post. You need to be more clear what the issue is. When do you get the error? What exactly did you do, or are you trying to do? No one can possibly know after reading the first post, we can only guess.
Just edit the shortcut with total commander on your device, or use notepad2 or something similar on your pc. Editting shortcuts is an important skill for cooking. That error occurs anytime you try to launch a program using a bad shortcut.
Click to expand...
Click to collapse
i get that error when i try to open the app.I haved extracted the camera(somehow) but now i get "Unable to initialize camera. Failed to set up the camera device".
PS: i'ved installed as an EXT pkg,now i get the same error "camera.exe couldent be opened..."
Well, if you're trying to port a camera from one stock rom to your rom, there could be a lot of things going wrong. It's probably not the shortcut (based on that error message), but more likely you're missing some key dependencies that the camera you want to use needs. I suspect there are EXT packages in the build that are required. I use an old Fuze camera, but these are the dependencies in the camera package:
CameraRc.dll
CameraRC_Launch.dll
CameraRC_Startup.dll
HTCCameraUtility.dll
Camera.exe.0409.mui
In the minimum, you probably need similar files. You may also need stuff like the correct mhub package (just a guess). You could also be missing registry keys that are needed.
Farmer Ted said:
Well, if you're trying to port a camera from one stock rom to your rom, there could be a lot of things going wrong. It's probably not the shortcut (based on that error message), but more likely you're missing some key dependencies that the camera you want to use needs. I suspect there are EXT packages in the build that are required. I use an old Fuze camera, but these are the dependencies in the camera package:
CameraRc.dll
CameraRC_Launch.dll
CameraRC_Startup.dll
HTCCameraUtility.dll
Camera.exe.0409.mui
In the minimum, you probably need similar files. You may also need stuff like the correct mhub package (just a guess). You could also be missing registry keys that are needed.
Click to expand...
Click to collapse
yes,i know that the error is because i miss some .DLL's,but i dont know witch DLL's...CameraRC_Launch.dll
CameraRC_Startup.dll i dont have this two :-?,below is my camera pkg
I dunno; I'm probably using a much older package, so the files could be different. You may not need the startup one. Try using one of the dependency tools on your camera.exe file to find out what libraries it needs to import.
Farmer Ted said:
Try using one of the dependency tools on your camera.exe file to find out what libraries it needs to import.
Click to expand...
Click to collapse
+1 for that!
hm...i need mhub library.but i dont know how to get it? :-s
i'm trying to extract Mhub(with all de dependencyes) library from a Xperia X1.....
i managed to extract the Mhub and mhubVO DOWNLOAD.The camera is working now but is missing some options,like the ressolution,delete picture etc! and now i have to find a complet camera.
i managed to get it working somehow,but now i get black screen and when i try to delete the taken picture crashes.Someone pls take a look at the EXT pkg ?
The easiest thing when trying to put together a package is to just test on your device. So, don't cook, then flash, then find out that things don't work. Instead, start adding files to your \windows folder until things work properly. You may need to re-file a module or two to do it, and you may also need to reset the device, especially if you over-write a rom file/module.
solved,from the pkg i missed to copy DDI.dll,now works just fine