hey all, I was poking around some kitchens trying to figure out how these devices work, and I was wondering if cooking oems into a rom puts them into the xip thus saving on running program memory as apposed to installing the cabs later. From what I understand, programs in xip execute in place, and are not loaded into ram. if this is correct, would that not be the #1 benefit of cooking your own rom?
I'm not very familiar with cooking roms and how applications are launched, but I can't see any way of launching an application or process without it being in ram. Storage is for storing files and ram is for running them.
these devices use what is called xip, stands for execute in place, allows programs to be ran from the rom, not the ram, I am just wondering if this is only true of programs in rom, or if programs installed after also utilize the xip feature
only ROM. xip images are fixed to a particular place in memory, which regular executables are not.
The #1 benefits of cooking roms is getting rid of carrier crap, newer possibly less buggy OS builds, building in your own customizations, and for many older devices you get to utilize otherwise unusable storage.
Related
Now, when it is possible to flash a custom ROM, but there is no a working tool to add a file to a ROM image, I'd ask people who are involved into ROM cooking to find a way to change page pool and flash partitioning. I believe these two things alone could be quite useful being applied to existing ROMs from manufacturer and operators.
I see the former is possible to (some?) ROMs for other devices. Trade performance for free RAM available or vice versa - isn't a good opportunity?
The latter means to re-distribute the user accessible flash storage between the main file system and the extended ROM. Of course, the primary intention is to add the space wasted by ExtROM to the user accessible pool
The latter also should reduce the number of people crying for unlocking the ExtROM on the latest ROMs and worrying about the warranty lost by Super CIDing at the same time...
DCD if you dont like what im doing just tell me to delete this post and i will.
All credit goes to DCD one of the best kitchen and Rom maker's out there.
If it wasn't for him our 6800's would be almost useless.
This is for the people who are using the titan kitchen. I took DCD's latest build and repackaged it for the PPCKitchen.org Titan Kitchen located
here http://forum.ppcgeeks.com/showthread.php?t=23206
Place it in your BuildOS/Kitchens directory and then extract "Titan_DCD_3.01_Selections.txt" and place it in the BuildOS/Projects directory.
Now you can create your own custom DCD rom using the new kitchen and DCD's latest build.
I've been using this for about 20 hrs and the rom is very stable.
Thanks again DCD u Da MAN!!!!!!!!
Make Sure to remove---> _fixed <---from the end of the file before u place it in the kitchens folder.
Download
http://rapidshare.com/files/108106961/Titan_DCD_3.0.4_FIXED.rar REALLY FIXED this time LOL
thank i'm looking for this. I ran into error error nk.dat
AstronusX said:
thank i'm looking for this. I ran into error error nk.dat
Click to expand...
Click to collapse
Sorry i forgot to change it from os.paylod to nk.fat, im up loading a fix right now thanks.
Errors in PPCkitchen
King - Thanks for putting this together
Unfortunately, I'm getting an error message (a bunch).
I downloaded the main file and did the updater.
When I go into BuildOS and select DCD 3.0.4 5054 or 5060, I am bombarded with error messages "Internal Error - Option.xml GUID not found (PROGRAM - xxxxxxxxxxxxxxxxxxxxx) where the "Program" is the name of the program and the x's are registry keys.
After I click ok 100 times to get through to the Kitchen, it allows me to select programs and build the OS, but once I install it, nothing actually gets installed on the phone.
Do you know what is causing this? Any help would be appreciated.
Thanks,
mfrish said:
King - Thanks for putting this together
Unfortunately, I'm getting an error message (a bunch).
I downloaded the main file and did the updater.
When I go into BuildOS and select DCD 3.0.4 5054 or 5060, I am bombarded with error messages "Internal Error - Option.xml GUID not found (PROGRAM - xxxxxxxxxxxxxxxxxxxxx) where the "Program" is the name of the program and the x's are registry keys.
After I click ok 100 times to get through to the Kitchen, it allows me to select programs and build the OS, but once I install it, nothing actually gets installed on the phone.
Do you know what is causing this? Any help would be appreciated.
Thanks,
Click to expand...
Click to collapse
Is this your first time using the kitchen?
King_tee - I had to do alot of editing to get ALL the errors to go away. I had to remove the welcomehead96.png, also had to remove a few other items.... like remotedesktop..... I guess I should have taken a log of what I did....
Edit - However - VERY nice job getting it to where it is..... Thank you
Thanks will try. The BuildOS in the regular kitchen is crashing so I can now cook a kitchen.
Also will my OEMs made for the 3.0.1 rom work if I put them in the build os directory. I didn't use the OEMizer w/ BuildOS. It appears to be the same just w/ a different save directory.
azclown said:
King_tee - I had to do alot of editing to get ALL the errors to go away. I had to remove the welcomehead96.png, also had to remove a few other items.... like remotedesktop..... I guess I should have taken a log of what I did....
Edit - However - VERY nice job getting it to where it is..... Thank you
Click to expand...
Click to collapse
No prob az i forgot about getting rid of those files. I thought i got all of them. I will upload a new file with the fixes for those who haven't downloaded it yet.
NEW FILE UP LOADED
Let me know if its working for you guys
As of this morning, the version I downloaded still gives an error (can't find HTC Sliding Sound module) when trying to load the selections.txt file for the DCD kitchen.
drgreenberg said:
As of this morning, the version I downloaded still gives an error (can't find HTC Sliding Sound module) when trying to load the selections.txt file for the DCD kitchen.
Click to expand...
Click to collapse
The sliding sounds module is in the DCD OEM's folder......when u open it up in the kitchen it should come up as a selectable OEM. At then point all you have to do is select it.
Bell?
Does the kitchen work for Bell phones? It does not seem to be in the carrier list.
jondixon said:
Does the kitchen work for Bell phones? It does not seem to be in the carrier list.
Click to expand...
Click to collapse
I don't know if it does.Are you are referring to the ppckitchen or DCD's Kitchen?
What i have provided is just a modified version of DCD's work (all credit goes to him) that will work in the ppckitchen.
You can check over here http://forum.ppcgeeks.com/showthread.php?t=23206
if you are talking about the ppckitchen, and they should be able to answer your questions.
If you asking about the DCD kitchen you can ask over here http://forum.xda-developers.com/showthread.php?t=385336 and im sure he will help you out.
I guess the obvious question is, what's the difference between the two kitchens?
DCD's kitchen is built around his ROM. The PPCkitchen kitchen isn't designed for any specific ROM or device.
Advantages of DCD's kitchen:
It's what DCD is using, so you know it builds his ROM like he intended it.
Advantages of PPCkitchen's kitchen:
Easy to install.
Prettier front end.
More error checking.
More OEMs to pick from.
Self updating.
Device dependency/exclusions supported
Carrier dependency/exclusions supported
OEM dependency/exclusions supported
Easy to move same configuration from one kitchen to the next.
Effortless switching between ROM configurations and kitchens
Splash/animation support
gguruusa said:
DCD's kitchen is built around his ROM. The PPCkitchen kitchen isn't designed for any specific ROM or device.
Advantages of DCD's kitchen:
It's what DCD is using, so you know it builds his ROM like he intended it.
Advantages of PPCkitchen's kitchen:
Easy to install.
Prettier front end.
More error checking.
More OEMs to pick from.
Self updating.
Device dependency/exclusions supported
Carrier dependency/exclusions supported
OEM dependency/exclusions supported
Easy to move same configuration from one kitchen to the next.
Effortless switching between ROM configurations and kitchens
Splash/animation support
Click to expand...
Click to collapse
I honestly don't think you give DCD enough credit for his work.... Here are some more Advantages....
Easy to use
Builds a basic ROM with only 2 clicks of the mouse.
Can be used behind firewalls.
No IP logging when you use it. (I had been told this was logged with your login name)
In all fairness both systems work very well, while the PPC kitchen has a more elegant streamlined interface, I do believe the end result is the same, a working ROM the way "I" want it.
error
hey guy anybody else getting an error unable to make file
when it goes to unpack the ppcgeeksoem rar
azclown said:
I honestly don't think you give DCD enough credit for his work.... Here are some more Advantages....
Easy to use
Builds a basic ROM with only 2 clicks of the mouse.
Can be used behind firewalls.
No IP logging when you use it. (I had been told this was logged with your login name)
In all fairness both systems work very well, while the PPC kitchen has a more elegant streamlined interface, I do believe the end result is the same, a working ROM the way "I" want it.
Click to expand...
Click to collapse
Could be because DCD has only a little to do with what we're talking about (which I gave him credit for). That's Bepe's buildos you're looking at, and essentially what we're comparing is Bepe's buildos w/ DCD integrated against PPCKitchen's buildos w/ DCD integrated.
You can't seriously suggest that Bepe's buildos is easier to use - the interface is practically identical! Both are about the same difficulty to use in their most basic, unaltered configurations, and both can build a basic rom w/ 2 clicks. Installing, configuring, starting, and maintaining is a lot different however...the nod hands down goes to ppckitchen there. Once you get past a basic configuration, PPCkitchen's buildos is unchallenged.
The proxy/firewall thing is fixed (general release this weekend) and it doesn't log IPs (never has).
Bepe's buildos get's the nod for no internet connection required, and the previous version (I don't know about v2) get's the nod for Linux compatible. Bepe's buildos also get's the nod for being more interfaceable to other projects and having more projects using it, but none of that is related to the original question (except maybe linux compatibility). [EDIT: v2 isn't native linux compatible, so no nod there.]
All of this is not too suprising, as PPCkitchen's buildos is, at it's core, an evolution of Bepe's Buildos.
I give credit to all sources DCD's kitchen / PPC Geeks kitchen and more.
They both offer the tools to make a ROM to your likings, some better then other, but the fact of the matter is that it gets the job done.
What PPC Geeks version is doing is making a bit more user friendly ( in my opinion ), but I still used DCD's kitchens because I really don't add any extra OEM's to my ROM's unless it is a specifically Themed ROM and then again I can get it done with both kitchens with ease.
I guess users will just have to test them both out themselves to see if they prefer one or the other.
What would be great is if we can have a Modifier / virtual simulator / kitchen where we can find ways to modify our ROM's / PPC's to their best potential ( such as drivers, RAM Management that works / compatibility with different OS and maybe interface change support ).
A virtual simulator to test out all of our modifications by simulating our respective device just as if we were to cook the ROM ( this could save tons of time rather then just flashing all the time or preventing an accidental bricking of your phone)
And a Universal kitchen for practically any Device ( well TITAN at least for our use ) that works on XP, Vista, MAC, and even Linux.
Im sure with all the developers on this forum and on ppcgeeks we would be able to get this done some time in the future.
Just an Idea....
[email protected]$ said:
What would be great is if we can have a Modifier / virtual simulator / kitchen where we can find ways to modify our ROM's / PPC's to their best potential ( such as drivers, RAM Management that works / compatibility with different OS and maybe interface change support ).
A virtual simulator to test out all of our modifications by simulating our respective device just as if we were to cook the ROM ( this could save tons of time rather then just flashing all the time or preventing an accidental bricking of your phone)
And a Universal kitchen for practically any Device ( well TITAN at least for our use ) that works on XP, Vista, MAC, and even Linux.
Click to expand...
Click to collapse
PPCkitchen buildos is actually the closest you can come currently for easily swapping components around, and there's a universal kitchen here on xda that supports many devices (way more devices than PPCkitchen does).
Don't hold your breath on the hardware emulator
lightbiter said:
hey guy anybody else getting an error unable to make file
when it goes to unpack the ppcgeeksoem rar
Click to expand...
Click to collapse
You'll have to elaborate a little better. If I had to guess, however, I'd say that you might have an older version of winrar installed. As a workaround, you can manually extract and modify the selections to use the extracted dir instead of the .rar.
I recently have found that to have a rom fit for my needs and to work properly with my exchange server settings, etc. that I need to rebuild roms (easier than starting from scratch). I am not planning on re-distributing them, they are mainly for my use, and others that use a specific exchange server setup like I do.
Anyway onto my main question:
Using the different tools I have found through Google and xda-developers, I have started to extract the radio nb file so that I can build a new NBH with the radio and the rom. I have also toyed with the idea to do the SPL into the NBH so that I don't have to worry if it has been flashed or not. I also will be flashing the roms from my microsd card (which I have been doing with my modified rom already).
Thank you in advance!
Putting an OS and a radio in a single NBH is perfectly acceptable. However, I don't think you can include Hard-SPL in there because it is flashed through SSPL, and it should really be the only thing flashed in that manner.
Trancecoder said:
Putting an OS and a radio in a single NBH is perfectly acceptable. However, I don't think you can include Hard-SPL in there because it is flashed through SSPL, and it should really be the only thing flashed in that manner.
Click to expand...
Click to collapse
Got it, thanks for the quick reply too!
I noticed your signature, and saw that you have the rilphoneauto. I see an EXT and OEM type file, but I am only familiar with cooking in cabs and making minor entries. I wouldn't know where to begin to add in an OEM or EXT to the roms that I modify/re-cook.
They're basically directories with a slightly varied structure that you put in an appropriate kitchen directory and then select inside the kitchen UI. If you're using the new "visual" kitchen, you should use the EXT package; otherwise the OEM. There are tutorials all over the forums explaining how to use them. I'm probably not the best person to do it anyway since I've only been cooking for a little while
please rom cookers have a look .can u guys cook rom for our device by this method .
if we got success in this matter no device will be bricked.
i m not so aware of technical terms .so i cant advice u guys!!
http://forum.xda-developers.com/showthread.php?t=520009
sorry for my bad english
i hope u will understand what i want to say
thanks!!!!!!!!
We are aware of this system, but right now, the system is under testing and not fully working. Rest assured when it becomes fully ready and if its possible to use it on gene, we will definately use it.
I said if it is possible, because, on gene, the concept of ULDR partition doesn't exists as far as i know. And ULDR partition is an integral component of that system. ULDR was most probably introduced in WM 6.1 but since Gene is a WM 6 device, it doesn't have the parition layout entry for ULDR. I could be wrong, this is just what my logic says based on my current information.
Also, it wont prevent bricking, as for the system to work, you will need to flash a ROM that supports the ULDR partition and the update system itself, before anything else. For that, you will need to patch your SPL as cooked ROMS will never have the HTC's digital signature. And as we know, patching the SPL is the reason behind all the bricking mess.
But anyways, thanks a lot for sharing
Double Post!
Will it ever work?
I have read the thread sometime back, but I have a few queries...
1. When you upgrade your OS from, say 98 to XP or XP to Vista, there always is a performance issue (compared to formatting your hard drive and doing a fresh install). And since our WinMo are nothing but hand held PCs (well you can say that, it got a processor, a hard disk (ROM), RAM), I guess that issue will crop up here as well.
2. What will happen if you have a 3rd party s/w which is incompatible with the new version of WM? Those of you who are in the PC tech field for a long time, you know after you have upgraded your OS, you can't use that software, neither can you uninstall it ...
So there will be issues, if I am not wrong.
But thats only my opinion. Most pple here are head and shoulders above me technically .
@Addicted: Well, Here are my opinions on your queries :
1. Yes, if the registry of the PPC is having some problems, then it will be an issue. Its a bigger issue in PCs as compared to PPCs coz in PCs the software are huge in size and they write thousands of entries to registry, modify system files etc. SO when an upgrade occurs, these changes either cause a corrupted registry, or in the second case when system files had been modified or replaced by a program, these files will be again updated by the OS and the program may not work, and if its a system level program with deep roots in system functionality, it will cause the system to slowdown at least or crash at worse.
These issues dont affect PPC much coz, for one, PPC software are usually small, they dont write much in registry (ms office on pc for example on PC writes a few thousand keys to registry while registering COM servers etc while MS Office on PPC just adds 10 or 20), and since the OS files are in ROM, they cant be touched by a software. They will remain overridden, if they have beem overridden as the updating process doesn't touch the phone memory.
2. Think again buddy, this is not applicable for WinMO. When you flash a ROM, you already change your OS version, so that will happen anyway, if you flash a ROM or you use the update system on an existing ROM.
I hope this would have cleared your doubts.
krazy_about_technology said:
2. Think again buddy, this is not applicable for WinMO. When you flash a ROM, you already change your OS version, so that will happen anyway, if you flash a ROM or you use the update system on an existing ROM.
I hope this would have cleared your doubts.
Click to expand...
Click to collapse
Actually you did not get me about the second issue, what I was trying to say is, if you flash your ROM, you incompatible program will be deleted (obviously) and thus free up space, but if you upgrade, your program will still take up space but will be of no use to you. Since most of the programs in Winmo are stored in Windows folder itself, it will be next to impossible for 99% users to identify the files to delete .
i already talk about image update in visual kitchen for gene thread, all this take lots time. da_g bepe and lots senior ppl are working on this its required new kitchen new rom format
as per i know it's required more rom space which not possible on gene rom
thanks !!!!!! guys for taking interest.
i like it because i have bricked my gene 4 times and got new motherboard.
but now my phone is not in under warranty so i cant take more risk.
i have done all methods correctly but unfortunately i was failed every time .
so after a year of trying i m still using wm5. so i want a new method without
zero risk for updating my rom.
Sorry buddy, but I dont think you can damage ur MB by wrong flash .
Over time several Hurricane have served as replacement parts for my Tornados, but they deserve a life of their own. So I have taken the effort of porting the Tornado Kitchen I had published also to the Hurricane.
I must tell you however that this device (also with the other available ROMs) has some shortcomings that I could not work around. The WM6 base and derived builds you could create with this kitchen can do the same (except some GUI tweaks that I have not ported) as the other available ready made ROMs, some things it can do better.
Same for all Hurricane builds (old or new):
no WLAN/WIFI (was never there - so no surprise, but some UI elements still list that)
Bluetooth cannot do A2DP well (stuttering, probably transfer speed?) but it stays in the UI (Settings)
GSM Radio (rilgsm.dll) does not support NITZ (automatic Time/zone setting - removed that from the UI) possibly other things as well. It will do the same as all other builds, just not as much as the Tornado.
memory card encryption cannot work (encfilt.dll is not loaded in XIP like in all other ROMs) still in UI though
keyboard hotkey assignment is different to Tornado (keybd.dll calls other .lnk files)
there is no SDHC support (but on Tornado)
Worse for this one (not anymore - updated ddi.dll available)
Display shows a quirk that the empty parts of the horizontal scrollbar are filled with random garbage when scrolling. No other side effects are observed yet.
Better for this one:
Hotkey handling built in (see Tornado Nitrogen Kitchen)
WMP Keys work for left-aligned (8200) and right aligned (SDA 2) music key layout. The WMP internal plugin can be disabled for device without music keys. All settings are done via UI.
You can cook in what you want or stay with the minimal setup.
Storage memory optimized - almost all items that can be UPX-ed (see my Tornado kitchen thread) are treated.
HTC Camera 4.0 could also be ported from Tornado build (also keeping the brightness bug with cursor L/R - use "Reset Brightness" to cure).
MMS/Camera integration is very good (heritage from efforts on the Tornado builds)
There is a working Direct 3D driver (d3dm_ti3d.dll) active in this build. It was supposed to work in the Tornado builds already (as modules there) but it did not. Taking the file versions from a shipped S620 ROM works ok. You may never notice the gap as hardly any smartphone application uses that D3D interface.
What is special about the Hurricane? Well quite many things that make it hard to cook for it:
It never had a native released WM5+ build. It seems that for Typhoon WM5 leaked once (Aleut's Typhoon builds are based on that as he told me) - and some parts of that leaked were also re-used in the Hurricane.
Several (quite many) OEM specific modules cannot be easily relocated as their .reloc section is missing (like for all WM2k3 retrieved parts). Hunting this down took quite some effort.
Only the wmreloc.exe can handle that properly and the builds that are created all work fine (except the display scrollbar quirk). No other relocation tools can handle that set of modules (I tried G'reloc, OSBuilder, ExtReloc, Platformrebuilder) so wmreloc is the wizard that makes it happen - so many thanks to the author:
Author: dysxq
Thanks: [email protected] http://www.oiopda.com.cn
The available Hurricane ROMs stem from a time where re-building a ROM seemed not to work easily and actions for most were done by manipulating a ready-made build to the cook's needs. This makes using them as a base for further cooking not so easy. Thankfully none of the authors has put efforts in "protecting" his ROM.
Hello!Waiting for the kitchen!!!I tried to disassemble the Rom with your programs binfiletools.zip.
Once converted the bin in nb0, i use os builder to dump files in the rom.
Then tried to remove the speaker, and add the Russian language. Collected Rom so well with Os builder. But it does not start on the Rom tmobile sda2. Although it has betrayed the boot OS, and I could make a Hard reset and soft reset!
Well, I had a discussion about the special topics of Hurricane ROM with the guys over at asusmobile.ru - and they concluded that OSBuilder will not be able to work on such patched old ROMs.
These are missing some essential information the OSBuilder relies on. So despite I like OSBuilder kitchen very much for its options - it cannot work with any of the Hurricane ROMs I have. Basically it will not remap the modules right and so your ROMs will not boot - no way to get that solved.
OSBuilder will dump everything correctly (as far I can judge) but rebuilding will always include the remapping step and due to missing info in most OEM modules they fail to re-locate.
The old kitchen I use (basically an adapted Nitrogen Kitchen for the Tornado) plus the wmreloc.exe will create booting ROMs.
When I find time I will have another try with the Chinese WM6.5 ROM, but I doubt that the OEM parts are much different.
You should also know that the XIP part cannot change much as the nk.exe (Native Kernel) is HW dependent. The nk.exe is very old and does not support the improved memory slot allocation of WM6.5. There is however not so much memory to manage on the Hurricane - so that should not be a problem.
The kitchen I intend to release will supply a bilingual English and German ROM that could be extended by more languages or have German be replaced by any other.
It is quite tricky though to have languages added, so I have to provide a rough guide to that as well.
Well, thank you! I'll wait for your kitchen!
Hello!How many days wait kitchen?)Thanks!
oh - well got other priorities. It is ready technically but the finetuning and description is pending - please some more patience. You could prepare in decomposing some existing ROMs with OSBuilder to see what is inside. This weekend - for sure
Hello, Thank you again, I already dump ROM files, and saw what's inside, but the problem was that I could not run the firmware on the phone! "Maybe I did something wrong did! So I'm looking forward to your kitchen! Thanks!