Related
I'm working on my ROM and I know how to disable My5 from starting, but what about the My5 files? Do they need to stay there? Which files are My5? How much space are they taking? Which can I take out? Etc.
Also, is there a CAB with My5 on it? That would allow me to set an option on my kitchen to either install or not install it...
I think the only way to do this is to cook the ROM yourself and delete these files prior to building it. I'm waiting for ITJE to upload his cooking folders so I can do this myself and free up about 1.5M of space.
mikenaustin said:
I think the only way to do this is to cook the ROM yourself and delete these files prior to building it. I'm waiting for ITJE to upload his cooking folders so I can do this myself and free up about 1.5M of space.
Click to expand...
Click to collapse
You dont have to wait.
Extract the stripped version
using my tutorial
Thats the version you are gonna get either by extracting it, or wait for me to upload folders, witch might take awhile.
cheers
But which files are safe to delete from the extracted folders? My kitchen would warn me of the files, if I could just get a cab with My5 n it... (It checks for duplicate files.)
I don't have the time right now, but I have to hunt down all the files I need to kill on your ROM in order for it to work on my kitchen. (The Comm manager for example (as you can choose between 4 or 5 different comm managers on the kitchen, but it'll give you an error if the ROM already has its own because of duplicate files.) And I still don't know what the differences between the Wing and the Herald are. Is it a simple registry entry that changes the keyboard layout? Any files change?
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,
let's keep the rom development topic in here. Here is my romkitchen, from kaiserkitchen 0.3. There is no flash utility, but you can use customruu for that.
The included rom is a base for localisation, or customisation. Click on first step (prepare), make your changes, then click on step 2 (cook). You have a Signed_RUU ready for flashing.
In my experience, it is best to delete the RUU_Signed before creating a new one
Also, the custom ruu will not flash the new rom if you do not change the folder between each flashing on vista. I use a name identation (folder1 then folder2, etc...)
Happy cooking. Please use this to help finding stuff about drivers
Warning: you cannot add or remove from sys folder without doing a greloc. DO it before doing anything. Notge the value, then relaunch it when you added or removed something. Put back previous value then click on go!
http://rapidshare.com/files/142122071/shiftkitchen.rar.html
thank you.
thaihugo said:
Hi,
let's keep the rom development topic in here. Here is my romkitchen, from kaiserkitchen 0.3. There is no flash utility, but you can use customruu for that.
The included rom is a base for localisation, or customisation. Click on first step (prepare), make your changes, then click on step 2 (cook). You have a Signed_RUU ready for flashing.
In my experience, it is best to delete the RUU_Signed before creating a new one
Also, the custom ruu will not flash the new rom if you do not change the folder between each flashing on vista. I use a name identation (folder1 then folder2, etc...)
Happy cooking. Please use this to help finding stuff about drivers
Warning: you cannot add or remove from sys folder without doing a greloc. DO it before doing anything. Notge the value, then relaunch it when you added or removed something. Put back previous value then click on go!
http://rapidshare.com/files/142122071/shiftkitchen.rar.html
Click to expand...
Click to collapse
Hi
Thank you very much.
Ram
Thank you for your hard work and dedication we put it. Best regards
thaihugo said:
Warning: you cannot add or remove from sys folder without doing a greloc. DO it before doing anything. Notge the value, then relaunch it when you added or removed something. Put back previous value then click on go!
http://rapidshare.com/files/142122071/shiftkitchen.rar.html
Click to expand...
Click to collapse
you mean that we have to extract sys folder from RUU_Signed.nbh file... then execute greloc and take note of the value... then copy files in the sys folder like OEMAPPS and OEMDrivers... and when we finish adding files in the sys folder... before we execute cook process and NBHutils we have to run the greloc again and reinsert the previous values... then click doit! in the greloc?
davidgreen said:
you mean that we have to extract sys folder from RUU_Signed.nbh file... then execute greloc and take note of the value... then copy files in the sys folder like OEMAPPS and OEMDrivers... and when we finish adding files in the sys folder... before we execute cook process and NBHutils we have to run the greloc again and reinsert the previous values... then click doit! in the greloc?
Click to expand...
Click to collapse
Make sure you keep your langugage specific folders intact.
Thanks
Ram
G'Reloc Situation
thaihugo said:
Hi,
Warning: you cannot add or remove from sys folder without doing a greloc. DO it before doing anything. Notge the value, then relaunch it when you added or removed something. Put back previous value then click on go!
http://rapidshare.com/files/142122071/shiftkitchen.rar.html
Click to expand...
Click to collapse
Hi thaihugo
My G'Reloc posts the same numbers always before and after, and strangely they are same for kaiser and SnapVUE. Am I doing anything wrong there?
Slot 0: 01F90000
Slot 1: 03DD0000
Size of ROM: 83400000
Unknown: 00000000
These are the numbers I have seen in ImageInfo.txt under .VM folder in SYS
Thanks
Ram
Most of the time, greloc sees the same numbers, but is needed for the few DLL's you have added. So even if you (as me) get the same number everytime, just run it to make sure everything is in place.
If you put say a full sys from another device, you will get slightly different numbers. You will have to put back the value you posted here in that case.
Morality: If you add any dll folder or exe folder in the SYS folder (not a simple dll or exe), do a preventive g'reloc before cooking.
thaihugo said:
Most of the time, greloc sees the same numbers, but is needed for the few DLL's you have added. So even if you (as me) get the same number everytime, just run it to make sure everything is in place.
If you put say a full sys from another device, you will get slightly different numbers. You will have to put back the value you posted here in that case.
Morality: If you add any dll folder or exe folder in the SYS folder (not a simple dll or exe), do a preventive g'reloc before cooking.
Click to expand...
Click to collapse
oh. Thank you
Ram
Help needed...
After all...i decided to cook my own rom...
Read alot , did everything i have read...
"cab oem" ing
"initflashfiles.dat" modification
but when it came to the end , buildos gives an error such as
The target file "temp\dump\mstscax.dll is a directory not a file"
Mind do wake me up for what i am missing ?
Safak
Help #2 for the noob
I have found out the problem about the previous tab... It was about wrong configuration of Remote Desktop...
I have overcome it but came a new one which is
Buildos gives this error
"Error building default.hv and user.hv"
and now , what ?
Help this poor lamer :-(
eh...
I ignored the latest error and have my own rom...and i m now flashing it to my Shift...
Will let yo know whn done...to be honest i m a little nervous about the result...
Urgent Help
I m in deep trouble...
I messed everything and now i m dead...Winmo side does not even boot...tell me what to do...tell me if there is a way to go back ?!?
how about flashing working rom to it?
omg
Recovered....thanks alot for your patience...
Average Joe
Hi guys,
I recently bought a HTC shift which SnapVue came out to be in Chinese, i really need to change the language and liberate it ASAP. I 've read so many replies on many different threads that i'm just completely confused right now. I barely understand all the technical words used out here. I need help please. Thank you.
What is the max size the rom can be?
I'm getting my Shift this week and I'm prepering for it with a cooked rom
EDIT: I saw that UDK's rom was 64mb in size so I know I'm safe if I'm within that limit
gullum said:
What is the max size the rom can be?
I'm getting my Shift this week and I'm prepering for it with a cooked rom
EDIT: I saw that UDK's rom was 64mb in size so I know I'm safe if I'm within that limit
Click to expand...
Click to collapse
Welcome Gullum.
64mb is the limit IMHO. Some NBH files over 50 mb have problems, and I have to reduce them.
thaihugo said:
Welcome Gullum.
64mb is the limit IMHO. Some NBH files over 50 mb have problems, and I have to reduce them.
Click to expand...
Click to collapse
ok first problem now ... I made my first atempt to flash a rom and now snap vue only gives a black screen what to do now?
edit maybe it should be added to first post that to recover from bad cooked flash then just flast the included rom
I now have a working own cooked rom on my shift just need to do some finetuning and I'll upload a rom for everyone to try... next step is to port a newer build.
i'm typing this on my snapvue side of my **** with opera mini
I have added some apps from blakstone and opal
google maps, rsshub, streaming media, calculator skined, thumbcal and some more
gullum said:
I now have a working own cooked rom on my shift just need to do some finetuning and I'll upload a rom for everyone to try... next step is to port a newer build.
i'm typing this on my snapvue side of my **** with opera mini
I have added some apps from blakstone and opal
google maps, rsshub, streaming media, calculator skined, thumbcal and some more
Click to expand...
Click to collapse
Hi
Can't wait. Could you check whether you are able to attach to audio to notes etc.
Thanks
Ram
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
Before i get flammed like crazy. I have searched for guides to cooking roms and used all different kinds of kitchens but none seem to work at all. Unless there is something written between the lines that i can't see i just don't think i'm doing anything wrong.
Anyway. When I try an build a rom and create the os-new.nb file imgfsfromdump just crashes and i can't create the file. Sometimes it works but once it fails it doesn't start working for a long time. I'm not sure what i'm doing. I try and dumb a stock rom and rebuild exactly the same but the same thing happens.
If anyone with some xip|sys porting could give me a hand to get past this step i'd appreciate it.
Thanks..
I'm starting to believe it might be a conflict with SP3. Can anyone confirm that they have these kitchens working with SP3?
replace your ImgfsFromDump with the attached version
itje said:
replace your ImgfsFromDump with the attached version
Click to expand...
Click to collapse
Thanks itje. I tried this but it still crashes everytime i try and compile the files. I'm not sure why. Is there something i could be doing wrong? Have you seen this before?
Did ImgfsFromDump ever work for you? (That is, did you try just extract and create the image without modify any content)
For me, I am not following the script in the kitchen completely to create the image. Here is what I execute on the temp directory (w/ dump as sub-directory) and work fine so far. (just make sure you did not remove the imgfs.bin and the payload in extracting the image)
..\TOOLS\ImgfsFromDump imgfs.bin imgfs-new.bin
..\TOOLS\ImgfsToNb imgfs-new.bin os.nb.payload os-new.nb.payload
..\TOOLS\NBMerge -kaiser os-new.nb
Strangly enough it did work a couple of times then i just started getting that error that says "imgfsfromdump needs to close" that basic windows error. I thought it might have been DEP but i made a exception for that program. I'm going to try this and see if i have the same problems.
I'M SUCH AND IDIOT!!! The reason it was crashing is cause i kept building the dump into packages. So i assume it was looking for files in the wrong place which just causes the process to fail. Thanks guys!!!
Can someone help me find this 21109 build to where i can actuallyt port it? I've tried to extract it from various roms and all it does is fail everytime and my phone is stuck at the sony screen.
*******EDIT******
I finally figured out how to get XIP ported but now i'm having a problem with the SYS folder. No matter what SYS folder i use and no matter how many different tutorials i go through i still get the same point. I flash and it sits at the sony ericisson symbol and does nothing. Is there some folders i shouldn't change in the SYS?
run g'reloc on the stock sys folder from x1, note all the values..
then run g'reloc on your new UNTOUCHED sys, where you change NOTHING...no swapping of files (unless you port from vga or qvga, or change locale, but thats another story) then change the values on the new sys with the values from the stock x1 sys, apply changes, and you have ported the sys.
cheers
itje said:
run g'reloc on the stock sys folder from x1, note all the values..
then run g'reloc on your new UNTOUCHED sys, where you change NOTHING...no swapping of files (unless you port from vga or qvga, or change locale, but thats another story) then change the values on the new sys with the values from the stock x1 sys, apply changes, and you have ported the sys.
cheers
Click to expand...
Click to collapse
When i run g reloc i get the same values as i did with the original build. Let me see if i understand the file hierarchy correctly.
1. I run G'reloc where i have my stock ROM's SYS folde. (note those values)
2. then i run G'reloc where my Donor SYS folder with the rest of the crap from the Donor ROM.
3.Then i copy the Donor SYS folder into the location i have my stock ROM SYS folder and overwrite. I run G'reloc again if the information is different from the first time i ran g'reloc i change it and hit do it.
Is this what i should be doing? I do this and i get the same result no matter which ROM i try and port from. I am porting from a touch pro ROM so is there anything i would need to change due to the vga to wvga switch?
swap from the modules marked with red to blue
base_dpi_192_resh_480_resv_640
to
base_dpi_192_resh_480_resv_800
since our device is WVGA you need to have the value set to 800 instead og 640.
So swap the folders with 640 from donor rom to the ones from either blackstone or x1
I can't get anything to work... If i extract the xip from this 21109 build that i have and try an use xipporterex to create the new xip and write it into the os.nb.payload and then merge the files. If i take that os.nb that is created i can build that and it will boot but if i try use the rom build procedure where it makes the os-new.nb file it will never boot. Even if i do nothing but just extract and rebuild the rom will not boot. From this i assume that i'm doing something wrong, 21109 build is corrupted or both. I'm not this inept. This shouldn't be giving me this much trouble with all these tutorials. Can someone please help me out with the exact procedure they use when building an X1 rom with porting over a new build?