Related
I'm working on a new dialer skin and I need a better way of reinstalling each time I replace images and need to test. Currently I am replacing the images in my base rom (thanx ivanmmj) then reflashing my phone. I need something really quick; like take the package file I have, replace the images, then convert to a cab file.
Attached is a sample of what I'm working on (thrown together REALLY quick as an example).
ICP-Fan said:
I'm working on a new dialer skin and I need a better way of reinstalling each time I replace images and need to test. Currently I am replacing the images in my base rom (thanx ivanmmj) then reflashing my phone. I need something really quick; like take the package file I have, replace the images, then convert to a cab file.
Attached is a sample of what I'm working on (thrown together REALLY quick as an example).
Click to expand...
Click to collapse
You'll have to get not only your pictures, but the rest of the package from my ROM, including the RGU's which are NOT included in the current ROM I uploaded. Remind me later and I'll upload it for you. As far as how to convert it... I dunno. I only make packages out of cabs, not the other way around.
ivanmmj said:
You'll have to get not only your pictures, but the rest of the package from my ROM, including the RGU's which are NOT included in the current ROM I uploaded. Remind me later and I'll upload it for you. As far as how to convert it... I dunno. I only make packages out of cabs, not the other way around.
Click to expand...
Click to collapse
I have the package, I just need a way to convert it back into a cab.
I'm also having issues with converting cabs to packages. I converted 'JUVS_HTC_Home.v2_1_1005722_s0.cab' to a package, added it to my rom, and it didn't work. I keep having the same problems with a few other cab files I tried. At least I got the touch dialer to work so I can test with it.
I initially used the T-mobile rom as a base to test with.
Glad you let me know about the rgu's before I tried flashing my latest.
I was actually just getting ready to flash your clean rom with my updates. I really need to start checking for rgu files first.
You should have no problems flashing the ROM. It's just that you won't be able to modify any of my current package settings without creating your own RGU's, me thinks.
If you're just trying to make a cab to install the files, post the files and we can help you make it.
Have you ever spent a lot of time on something, just to find out someone else made a quick and easy way of doing it:
TDial Designer
It took me 10 minutes using TDial Designer to do what I did in 2 days using Photoshop.
Ok, I guess I will start on the CommManager skin then. After that, the Calculator.
As far as i know - when you have to package files. jsut copy them to the device.......
you don´t have to make a cabfile out of them. only copy...
But i never tried..
Today I just tried this, I compressed my softwares which I have cooked in my ROM using UPX4PPC and cooked them in the ROM. As I have a small 32MB ROM, if this is possible to do with the default OS dll & exe files, it would be very useful. As I noticed, there is no big difference in the loading time of compressed files & the original. I searched the forum, but found nothing on compression of system OS files. Is there anyone who have done this before? Is this ok to do with .net CF dll & other large dll & exe files in ROM...?
making a smaller rom dont give more storage you know?
so compressing it will just give you more empty rom space nobody an use
Yeah..and most of the time the ROM won evenstart..blv me i tried to UPX the whole DUMP folder but the rom didnt even start
Rudegar said:
making a smaller rom dont give more storage you know?
so compressing it will just give you more empty rom space nobody an use
Click to expand...
Click to collapse
Actually I meant, If you can compress the originam OS files in ROM, there would be more free space in rom. We can use that free space to add more OEM packages.... Sorry if my english is not clear.
ather90 said:
Yeah..and most of the time the ROM won evenstart..blv me i tried to UPX the whole DUMP folder but the rom didnt even start
Click to expand...
Click to collapse
Try to use UPX only in exe files. More safe to be use in EXEs that are loaded after the booting & intended only in doing the settings (backlight.exe, MicAGC, Device info, CSD line type, CommManager, faxView.......) and on OEM exe files. Try not to use on dll files on first shot. But because already these files are very small, you will gain only a very small space. It works. If we can do the same on large dll files, it would be cool.....
shiranmotha said:
Actually I meant, If you can compress the originam OS files in ROM, there would be more free space in rom. We can use that free space to add more OEM packages.... Sorry if my english is not clear.
Click to expand...
Click to collapse
You are right. Thats how I had been able to pack so much extra stuff (many dont like that) in the ROM since a long time. But you have to be very carefully choosy about the files you have to UPX.
And, of course this method is for cooks only...
c_shekhar said:
But you have to be very carefully choosy about the files you have to UPX
Click to expand...
Click to collapse
What files can we compress. What I found ws, when I compress certain dll files, some items in menus related to them are blank. But when clicked they still work. Compressing Today dll files work, but if they have option configuration, they show some nunsence text. DLLs related to the .NET CF are the largest files i find in the ROM, can we compress them?
shiranmotha said:
What files can we compress. What I found ws, when I compress certain dll files, some items in menus related to them are blank. But when clicked they still work. Compressing Today dll files work, but if they have option configuration, they show some nunsence text. DLLs related to the .NET CF are the largest files i find in the ROM, can we compress them?
Click to expand...
Click to collapse
use the option for not compresing the resources
Hi,
I am looking for a utility to merge multiple small ( free ) utilities into a single .cab file to automate the installation; just to ease the installation process after the hard reset or ROM upgrade.
Though i tried Win CE Cab Manager but unable to achieve that functionality - its look like to me that i am missing something somewhere.
Regards.
I'd like to know this too...
Does this help? Not used it myself
http://forum.xda-developers.com/showthread.php?t=392983
mic_888 said:
Does this help? Not used it myself
http://forum.xda-developers.com/showthread.php?t=392983
Click to expand...
Click to collapse
Thanks mic for the link... But according to that software ... one have to place all the required cab files in a specially designated directory and software start installing the files from there one by one...
But; what i am looking is a software that creat a single .cab file which includes all the required ( individual ) cab files along with the parameters e.g. installation location ( Device or Storage Card )....
sashami is the best solution which was actually inspired by a script called autorun back in the days of win mo but only way to do a auto install of cabs or all one one would be to attempt and cook into you're own rom or see if it's possible to cook all cabs into 1
Maybe extract all cabs with ini or XML file. Merge ini or XML place all extracted components in same folder and use cab building program to build cab from ini/xml...
Maybe.
This is the best thing I have found........not really an app per se.
What is UC? It is a feature contained in UC capable ROMs. A UC capable ROM extends initial customization to your SD card so you can load cabs and install XML files that are located there too. What this means is that once you get your customization scripts right, you can flash any UC capable ROM and all your apps and settings will be restored as part of the initial customization process whenever your SD card is inserted in the slot.
http://forum.xda-developers.com/showthread.php?t=366337
I have been using Slueth's ROM and this UC method for quite a while now and it works fantastically. Takes a little effort but anything worth it's oats will take atleast a little effort.
http://forum.xda-developers.com/showthread.php?t=366284
I just come a across while searching, here is another solution:
http://www.pocketpctoolkit.com/
this should not be a advertisement, because it is not freeware, but a suggestion.
you can add cabs and the program builds an desktop or device installer and merges the cabs (and other files). the device installer is a exe not a cab....
if you look deeper in the internet you find a full time solution...
hope it helps...
chipsxj said:
This is the best thing I have found........not really an app per se.
What is UC? It is a feature contained in UC capable ROMs. A UC capable ROM extends initial customization to your SD card so you can load cabs and install XML files that are located there too. What this means is that once you get your customization scripts right, you can flash any UC capable ROM and all your apps and settings will be restored as part of the initial customization process whenever your SD card is inserted in the slot.
http://forum.xda-developers.com/showthread.php?t=366337
I have been using Slueth's ROM and this UC method for quite a while now and it works fantastically. Takes a little effort but anything worth it's oats will take atleast a little effort.
http://forum.xda-developers.com/showthread.php?t=366284
Click to expand...
Click to collapse
i flash phones like everyday. using that method is for doing a couple of cabs. if you are trying to do like 100 cab files it will take a loooooooooooong time.
wince cab manager
if you just want to make one cab i would use Wince Cab Manager (OCP Software) (google it) to extract all the neccesary information from all the cab files.
then re-import all the information (links, registry, files etc) into a brand new Cab File.
so long as you keep all the extracted cab files separated this should be easy enough, but time taking.
Hope that helps. =D
Dan
I am a software developer by trade and so I hope I will be comfortable with creating my own ROM. However, I have no idea where to begin! Can anyone point me in the right direction?
on the wiki you can all read about it.
xmoo said:
on the wiki you can all read about it.
Click to expand...
Click to collapse
Thanks for the quick replu xmoo. I've had a look there before but it's not answering any questions. I have no idea what dev environment I need nor how to do it. Am I missing something or is it just my Sunday head?
you need a kitchen, in the kitchen you unpack a ROM image, you then exchange, remove or add files to the extracted ROM image. then you repack it. thats it. no programming skills involved.
and all information regarding kitchens can be found in the wiki, I did at least.
schaggo said:
you need a kitchen, in the kitchen you unpack a ROM image, you then exchange, remove or add files to the extracted ROM image. then you repack it. thats it. no programming skills involved.
and all information regarding kitchens can be found in the wiki, I did at least.
Click to expand...
Click to collapse
Thanks for the info.
I have Hard-SPL'ed my X1 and am ready for a new ROM now. I have downloaded a NBH file and used the NBHUtil to unpack it. Is this the point at which I customise the individual parts? If so what do I use to do this with the NB files?
NBHUtil is not a kitchen, its a utility only. And NB files are just the components of the NBH file, like a NB for the radio part, a NB for the OS part, a NB for ... you get the idea. The actual contents (exe, dll, eg.: files that ARE windows mobile) are encoded inside the NB's.
Search for "RaphaelKitchen" version 0.62, download that. Once you got that far, get back in here and I'll give you the config files you'll need for the RaphaelKitchen.
Instructions on how to do what: http://forum.xda-developers.com/showthread.php?t=427507
In that message, leave out the parts about dumping and get directly to the instructions for the kitchen. The actual "cooking" (thats what its called, hence its called a kitchen) comes between instructions "e, b (for dumped ROM),space key" cuz now you just unpacked the ROM and you have tons and tons of DLLs, EXEs, eg.: you unpacked the NBH in NBs and decoded the NBs to its contents.
You cook by removing and adding stuff to the respective folders.
After you did that, continue by following the post: "c, a, press BuildOS Play icon and wait to finish, Close BuildOS, close PagePool Changer and press space" which equals putting the files back together and compiling a new NBH which you can flash...
and i'm sorry but the WIKI acutally REALLY does explain all that:
http://wiki.xda-developers.com/index.php?pagename=Kaiser ROM Kitchen Tutorial
The RaphaelKitchen is a modified version of alex kitchen for the kaiser, it is essentially exactly the same.
Cheers Schaggo!
I was looking at the Xperia Wiki not the main Wiki My bad sorry.
I'll give this a go later and report back
No problem, no problem. As I said, as you start cooking, get back in here and I'll provide pre-edited config files with all the settings for the X1.
schaggo said:
No problem, no problem. As I said, as you start cooking, get back in here and I'll provide pre-edited config files with all the settings for the X1.
Click to expand...
Click to collapse
Hi, could you provide the pre-edited config files for X1? Thanks.
Ok so here's what I have done:
Download and unpacked RaphaelKitchen 0.62 as stated.
Ran it with 'e' then 'a' as the command line parameter to extract the NB files again (just to see).
Found all the NB files in BaseROM folder and a sh*tload of mixed files in the temp folder. At the root I have a couple of BIN files as well as some NB related files. dump_imgfs and dump_xip are the main folders in there with lots of bits beneath then. Is this right?
Then ran the build ROM commands as you stated. Pagepool wasn't open though(?) or couldn't see it anyway. Everything else went to plan and I got a NBH file in the end.
I expected the packages folder to be populated but nothing went in. Has this all gone to plan?
**Edit: Also never saw PagePool **
Here is the extra config you need for X1
Extract and put the files in the root of the RaphaelKitchen.
Run "X1Kitchen.CMD".
This is what I am using for "e"xtract and "c"ook a room and it's working perfectly w/ me. Other options is not tested or use by me.
I even added/modded some more files. Replace all files and run RaphaelKitchen.cmd and continue as instructed in the manual.
Cheers guys. Will try this config tonight and get back to you
In the extract ROM there are two options:
- one needs RUU_signed.nbh only
- the other one needs RUU_signed.nbh + part01.raw and part02.raw
which is the right one to choose? if b): where do i get those files?
/edit: never mind, figured it out myself
Flashing now :-D
For future reference, if some more people ask:
if you just want to unpack an existing ROM image (nbh-file) use option 1. this unpacks the file and fills up the folders with the files to cook with.
if you want to reconstruct a ROM you (or someone else) dumped from his device, chose option 2. this decodes the raw-files (dumps) according to (simply spoken, please forgive my inaccuracy ) the template which is given by the nbh-file. without the nbh-file the kitchen doesnt know how to decode the raw-files, it needs a reference file (the nbh) to do so.
hi i'm a noob to the whole wm scene and i'd like to learn how to cook my own roms as well. I've downloaded the kovsky kitchen but i can't find anywhere on how to use it. i've looked in the wiki but can't find how to use kitchens. maybe i've overlooked something. at any rate, if someone could post a link on a tutorial or any info that could get me started, it'd be greatly appreciated. thanks in advance
figurine said:
hi i'm a noob to the whole wm scene and i'd like to learn how to cook my own roms as well. I've downloaded the kovsky kitchen but i can't find anywhere on how to use it. i've looked in the wiki but can't find how to use kitchens. maybe i've overlooked something. at any rate, if someone could post a link on a tutorial or any info that could get me started, it'd be greatly appreciated. thanks in advance
Click to expand...
Click to collapse
take yer pick, but the first one looks okay!
http://www.google.com/cse?cx=000825...orial&sa=Search&cof=FORID:0&ie=utf-8&oe=utf-8
thanks! one more thing... should i backup my original rom? if so, how do i do this?
Hypercore and X1 "kovsky"
i just had to ask, well kovsky kitchen works for the experia right? so hypercore multidevice, shows no experia or kovsky config, #11 post says raphael kitchen xperia.cmd, so you can use that kitchen for x1 as well, so how do you get hypercore/X1? to work
Hi all... (sorry for my english)
I'm a noooooooooooooooooooob chef and i have some questions for you...
I cooked my first Rhodium ROM , but i have this problem:
When i tap on some program, i have an error message!!!
This error message tells me that you can not start the application because you can not find some components of the program, or you do not have a valid certificate...
PS: I think this is the same problem for which does not start the Sense 2.5!!!
I use "Rhodium Native WM6.5" (OEMXipKernel + os.nb.payload + romhdr.bin) with "buid 21864" (xip.bin + MSXIPKernel + SYS), and i have replaced in SYS folder NetCF2.0 with NetCF3.5 (i have moduled a cab file)...
I have tryed to use Leo EXT and Rhodium EXT, but i have the same problem!!! And i have the same problem also with NetCF2.0...
Where i wrong?
possible that no one can answer?
but I'm on XDA or not?
That error means that you are missing some dependencies. Use PE Explorer or Dependency Walker againt all exe and dll's in the package that you are having the errors on. You'll get a list of dll dependencies. Find out what packages have those dlls and include them in your rom.
Good luck.
either this or try opening the exe's from you're windows folder, this will tell you if you're shortcuts are bad.
if I understand correctly I have to check all .exe .dll and .dsm files? right?
dependencies defined in this files? and with the previous tools I can decipher the dipendencies?
Now I procure the tools ... thanks for the help ...
Well .. it seems that things are clearer now thanks to you ..
I used "Dependency Walker", and I looked the exe file of the EXT that does not work on my ROM... I realized that there are some missing .dll files that should be in the EXT folder called "files", but there does exist...
If I dumop the Shipped ROM where I took the EXT, I find them?
joshkoss said:
either this or try opening the exe's from you're windows folder, this will tell you if you're shortcuts are bad.
Click to expand...
Click to collapse
sorry but i don't have understand this method...
Can you explain the procedure in other words?
I'M REALLY SORRY FOR MY ENGLISH...
ciko84xp said:
sorry but i don't have understand this method...
Can you explain the procedure in other words?
I'M REALLY SORRY FOR MY ENGLISH...
Click to expand...
Click to collapse
it's ok man!! head over to my kitchen thread: here. Download my kitchen and read the tutorial's on the first page...
Good work my friend.. your kitchen and your tutorial's are really useful for a noob chef like me...
Now I have one question... if I use "Depenadancy Walker" for open the .dll files inside the EXT package that I want to cook with my ROM, I understand that I need some .dll files to put in "files" folder of the EXT in question... at this point, I search the missing .dll files in "dump" folder and I find them in OEM folder...
the problem is this: if I follow the way to arrive at folder where are the .dll that I need, I can't find it... it's impossible to see the file.. I see only 4/5 white files called "S000", "S001", "S002", "S003", etc etc... but I don't find the .dll file that i need...
WHY????????????
ciko84xp said:
Good work my friend.. your kitchen and your tutorial's are really useful for a noob chef like me...
Now I have one question... if I use "Depenadancy Walker" for open the .dll files inside the EXT package that I want to cook with my ROM, I understand that I need some .dll files to put in "files" folder of the EXT in question... at this point, I search the missing .dll files in "dump" folder and I find them in OEM folder...
the problem is this: if I follow the way to arrive at folder where are the .dll that I need, I can't find it... it's impossible to see the file.. I see only 4/5 white files called "S000", "S001", "S002", "S003", etc etc... but I don't find the .dll file that i need...
WHY????????????
Click to expand...
Click to collapse
First off... usually you need the entire EXT package that contains those dlls.
Second, the dlls that are directoried are actually modules. Leave them as is and include that EXT package in your ROM. You only need to recmod modules and convert to files "if" that package is giving you problems with platformrebuilder.
Third, Any package that you include from a dump, you need to look inside the initflashfiles.dat and see if there are any entries for the package you are including. You can either add those to your initflashfiles.dat or as I do, copy them and create the app.dat file for your EXT package.
Is there a guide to help noob cooks? I want to try getting into it, rather than just testing everyone else's, but I have no clue where to start.
ianderson_76 said:
Is there a guide to help noob cooks? I want to try getting into it, rather than just testing everyone else's, but I have no clue where to start.
Click to expand...
Click to collapse
There are a lot of thread. First thing you need to learn being a chef is know how to search. Use the link in my sign to search. Search for kitchen in this forum, and you will find tons of info. Read, keep reading, flash, keep flashing...thats the only way to cook a good ROM.
I think all the help given to the OP is what makes this forum...