Hi,
I've extracted some ROMs and built my owns and I realized that in the newer ROMs a lot of .dsm files are present. I think these can be deleted just as the .rgu files can, because as far as I have tried it, they are only necessary for building the ROM from its parts but now for assembling/running it. Would save some space...
Regards,
Stefan
Related
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 all
it's already few days (and nights) that I'm looking for how to dump my french rom and I managed to dump the raw parts O 1 2 3 following all the tutorials with the tricky memory adresses but I cannot manage to rebuild it then
I extract it throught the kitchen after havin put the parts and the ruu signed in the baseRom folder but when i try to cook it with the builOS program
I indicate the ROM folder but there is always the file OS.nb missing
I have only a folder XIP with a file called boot.rgu inside the ROM folder
I had a look in the whole kovskykitchen folder, there is no OS.nb, just one called OO_SPL.nb created after extraction in the base ROM folder.
did I miss a trick ? sorry if so but I didn't find any help in the threads...
thanks guys
bill'o said:
I had a look in the whole kovskykitchen folder, there is no OS_SPL.nb, just one called OO_SPL.nb created after extraction in the base ROM folder.
thanks guys
Click to expand...
Click to collapse
Have you tried copying 00_spl.nb to OS_SPL.nb and then re-building ?
sorry the file needed is called OS.nb and not OS_SPL.nb
yes I did it, rename the file 00_SPL.nb by OS.nb and put it the ROM folder,
then I indicated it into the buildOS soft package tool, it looks like it is workin fine and finish sayin work successful then I close it,
the dos window takes the relay but displays an error 'input file OS.nb.payload has no valid boot sector aborting...'
that's rude right ;°) ?
bill'o said:
hi all
it's already few days (and nights) that I'm looking for how to dump my french rom and I managed to dump the raw parts O 1 2 3 following all the tutorials with the tricky memory adresses but I cannot manage to rebuild it then
I extract it throught the kitchen after havin put the parts and the ruu signed in the baseRom folder but when i try to cook it with the builOS program
I indicate the ROM folder but there is always the file OS.nb missing
I have only a folder XIP with a file called boot.rgu inside the ROM folder
I had a look in the whole kovskykitchen folder, there is no OS.nb, just one called OO_SPL.nb created after extraction in the base ROM folder.
did I miss a trick ? sorry if so but I didn't find any help in the threads...
thanks guys
Click to expand...
Click to collapse
It's all in here: http://forum.xda-developers.com/showthread.php?t=446691
no, this still doesnt fix the Could not find the file 'C:\KovskyKitchen\ROM\ON.NB'
issue??
I recently upgraded my XPERIA X1 to Windows Mobile 6.5 using the W4X ROM however I'm disappointed the a majority of the ringtones have been removed.
I'm curious whether they can be extracted from a NBH image.
Now, firstly, I have no idea how to cook a ROM but I imagine the files and folders are contained within the image file somewhere.
I have a backup of the previous official R2AA rom that came pre-installed with the device however I have no idea on how to extract the NBH file.
I found an application that splits the NBH into several NB files however I have no idea how to progress further.
I imagine the 'Windows.nb' image contains the contents of the Windows folder on the device where the ringtones would be.
So, could someone point me in the right direction to find an application that will allow me to extract the folders contained within the NB file so I can access the missing ringtones and reinstall them?
Cheers,
Hyped
hypedupmonkey said:
I imagine the 'Windows.nb' image contains the contents of the Windows folder on the device where the ringtones would be.
So, could someone point me in the right direction to find an application that will allow me to extract the folders contained within the NB file so I can access the missing ringtones and reinstall them?
Cheers,
Hyped
Click to expand...
Click to collapse
if you download jerpelea's kitchen (it's in one of the stickies) and put the rom in the source folder then run the command it extracts everything from it, and i suppose you could probably browse through the files that way, but i'm nt sure, just a suggestion!
or you could probably search for the ringtones on XDA, i know there are some from the rhodium somewhere!
Search this forum and you will find plenty of ringtone packages to download (removed from ROM but as addon shared by the cooks)
Thought gtrab shared it also in his cooking tutorial....
I just noticed something.
The first time you extract an *.nbh Visual Kitchen puts a *.cer file in Tools Folder for every package of the ROM.
I am cooking ROMs for a year now an i never had even one *.cer file in this folder but the rom always worked.
So are these *.cer files needed for something anyway?
Maybe they are needed if you use an EXT Package from a different phone?
Hi,
I have a ROM, for example Enomther's. and I also have the arabic language libs. how can I integrate the arabic libs into the ROM's zip file so I don't have to flash another zip for arabic libs? I have attached the arabic libs.
Bump! anyone?
Come on, what kind of answer do you expect?
Here's the answer: you need to substitute the files in the original ROM zip and resign it - that's it.
Now you're going to ask, how to do it, because you have no clue - and the explanation is a lot of work to try and put in one post, and setting up signing applications involves installing Java SDK and some knowledge. If you're asking the question you're asking - it seems like you're far from being skilled enough in Android depths to do what you're asking to do, and that's why you see no answer. After all, if you'd want to do it - you'd have to search anyway, Google "sign apk zip" and here you go, a lot of tutorials show up. And if you didn't search and posted instead - it speaks for itself.
By the way, there's no good reason to integrate the libs into a standard ROM, moreover - it's a bad idea. ROMs tend to be updated, and the work that needs to be done setting up the environment for signing APKs and ZIPs is way more than flashing one update right after updating the ROM to a newer version. And ROMs are updated quite often.
Yeah i'm not skilled. I'm trying to learn... I am trying to make my own customized ROM for my country's users. And I didn't mean editing ROM files, I was saying how to push the lib into the ROM zip so people don't have to flash the arabic zip lib when they flash my customized ROM. So I hope you haven't missunderstood my question...
Ah, I see, you want to customize and share the ROM. In that case, you have to have the setup I'm talking about. The update.zip contains folders and files, which directly replace the files in the same folders in ROM, so if you have a ROM zip - you need to replace those files. The easiest way would be just extracting your update.zip, opening a ROM zip in 7zip / WinZip / WinRar / etc, putting those extracted files from update.zip in the right place into ROM zip by drag-and-drop, and then resigning the ROM file.
Please do some googling as to how to sign ZIP and APK files. There are some pretty good tutorials.
I have done that before, and I replaced the lib file with the ROM default lib. it's libskia.so, but I think because I didn't know I have to sign it it gave me an error while flashing through recovery. so after I replace the lib I have to re-compress the file and then sign the zip right?
You don't have to re-compress if you replace the file without decompressing the original ROM archive, by dragging-and-dropping the file into the archive.
And yes, you have to re-sign the ZIP after any changes you make to anything inside it.