Related
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.
First things first! As the topic states, this is a *TEST ROM*
DO NOT expect this ROM to be usable for every day use
DO NOT expect this ROM to be well tweaked for performance
DO NOT expect this ROM to ... you get the idea, i hope!
This is the first Test ROM for the Image Update service - this ROM has a 1024KB free space buffer for NK partition, 20MB free space for OS partition. This should be enough to facilitate several ImageUpdates for testing. (It's not intended to have enough space for you to add all your chosen apps for every day use - this is just for TESTING!)
It's based on WM 6.5 21812. This ROM is unique in that both the NK and OS partitions are completely uncompressed, rather than using either XPR or LZX - so i'm testing that too. Please report on overall system performance of the BUILT IN applications (not cabs or packages you install) - i'm wondering if Uncompressed is viable at all vs. XPR and LZX. So far i'm thinking no (60MB LZX -> 80MB XPR -> 150MB Uncompressed) - but testing is warranted!
The Image Update packages for this ROM are now in post 2!
Here's the download link!
Again, this is BAREBONES, the ONLY thing it has is drivers and comm manager, this is done on purpose, so that we can have as few variables as possible while testing deployment
http://rapidshare.com/files/244900505/ImageUpdate-ready-ROM-Raphael.rar
Some notes:
The ROM has an OS pagepool size of 26MB
The ROM has a ULDR pagepool size of 4MB (up from 1mb)
All compression is disabled entirely (not XPR or LZX, but Uncompressed - both on NK and OS partition, also compression is disabled on individual modules and files)
Dr. Watson (Error reporting) buffer reduced from 300K to 0K
Update Packages
QuickGPS
EzInput+eT9
Camera - This will install the Camera, Dshow, Mhub, and SensorSDK packages (Camera is dependant on the others)
Here's the test case scenario - create a directory named "Release" in your filesystem, at the root \ folder (so \Release)
Copy the cab.pks to your device, or sd card, and run it as you would a cab
Note any errors or anything that might occur before the process succeeds or fails
If the process fails - please attach the logs found in \ and \Release to a post, so we can analyze it further
If it succeeds, time to hard reset your device!
Check and see if the package remains after hard resetting.
If it does - We have a winner
A live-updating rom with no need to reflash the device after each upgrade? I love it!
Keep up the good work!
Interesting concept.
this is awesome! cant wait to cook one for kaiser(hint, hint) thanks for all your work, this is going to change EVERYTHING.
Image Update System
I have been following the WM Image Update System thread and the idea sounds very doable. How can we help?... David.
I can Hard reset my phone every day, so if you in need of any volunteers Im here .
I have been following your kitchens for a while, and it's time to return the favor.
Thanks so much for your hard work Da_G!!
-------
HTC Fuze - WM6.5 21812
Da_G...Sir, you are a saint and a scholar...when this is finished it will be the coolest thing since velcro...
I would love to help just let me know how...would be happy to test..report...etc.
Dreaming of the day...no more hard reset
Da_G,
Thanks for your hard work.
I'll been dreaming of the day when I don't have to reflash my ROM or hard reset just to update the software.
I'll beta test and give you report.
D/Ling now, will report after work this evening. :excited:
i am really enjoying the speed. its unreal. every thing else seems normal. i am still loading up my apps right now. i'll post up some more when i get home.
the speed and respon se is secon d to none . i am very much plea des with the performance .
i know you said its barebo nes....so. i will view the lack of came ra e xe and .net. fram ework as by design . let me know if there is anyt hing spe cific you want me to test .
rzanology said:
the speed and respon se is secon d to none . i am very much plea des with the performance .
i know you said its barebo nes....so. i will view the lack of came ra e xe and .net. fram ework as by design . let me know if there is anyt hing spe cific you want me to test .
Click to expand...
Click to collapse
I'm going to need you to test your awesome space bar, it seems to be more than working well... =P
LOL, didn't overwrite CompIME.dll in this release (again for compatibility reasons) so that's why the jacked up spacebar..
But hey, it's a test
Hoping to have packages for you soon
Everything is working smoothly, no issues yet. I read your other post on the image update and want to know how far into user customizablity we can go without messing up the update process, ie. regedits, packages, etc.. Or if its a secure core that we can't really mess up.
Oh, yeah, its supper snappy and extremely responsive. And running at 26% Memory isn't bad either.
Is it safe to assume any updates needed to be deployed, such as over writing the CompIME.dll will be done thru the this new Updating system, correct?
Thanks for your hard work Da_G!!!
So, am I correct that any chefs who want to incorporate the working updating system into their roms will have to cook unprotected? This could get really interesting, LoL.
Thanks for the awesome work!
@Farmer Ted:
Yes, to support Image Update, ROM's will need to be fully "unprotected" - protection is really just damage to the ROM structure that still allows the phone to work
@NFRCER:
Yep, that will be one of the first test packages probably
@danthman2000:
The only thing you need to be concerned about in doing mods is that any files you replace or registry settings you change that might be in a future update, the update will not apply them, unless its specifically set to override your settings by using an mxipupdate_*.provxml - but the creator of the package should be aware of this before hand - so if it needs to override any of your settings it should be set to.
By the way, I plan to have the first test .cab.pkg up by tomorrow, so if you're sitting there with the test rom flashed, might wanna go back to a working one for now
Da_G said:
@Farmer Ted:
Yes, to support Image Update, ROM's will need to be fully "unprotected" - protection is really just damage to the ROM structure that still allows the phone to work
@NFRCER:
Yep, that will be one of the first test packages probably
@danthman2000:
The only thing you need to be concerned about in doing mods is that any files you replace or registry settings you change that might be in a future update, the update will not apply them, unless its specifically set to override your settings by using an mxipupdate_*.provxml - but the creator of the package should be aware of this before hand - so if it needs to override any of your settings it should be set to.
By the way, I plan to have the first test .cab.pkg up by tomorrow, so if you're sitting there with the test rom flashed, might wanna go back to a working one for now
Click to expand...
Click to collapse
A working one? This one is working beatifully lol .
Im curious, I checked the system tab, and I didnt see the Windows Update Icon...
How will we check for the update then? Just wondering, thats all.
My apologies if im asking too many questions
Great news Da_G. I'll test it once you post the update tomorrow. How do the updates get delivered?
Is the .cab.pkg a small file which contains the server information so the phone can go out and retreive it? Or is the .cab.pkg the whole kitten caboodle?
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!
Hello, I am DRS, and wanted to expose an idea that I've been maturing.
First say that my knowledge of android are very basic and that is just an idea, not whether it will be possible to make it happen, so I ask helps if you have advanced knowledge of android, I start to explain the idea:
It has occurred to me that maybe the rom change process can be simplified by a .... I'll call "linker", we split:
1. Always start from the device has the original rom the manufacturer.
The user chooses the "linker", which is actually an application on your android.
2. This "linker" collects and stores the user's selection may be the kitkat, jb, gb .... depending cooked roms have the sd card.
3. The "linker" will catch rom Gapps original comparing it with the new cooked and "keep" new Gapps launcher and cooked rom New rom.
4. To finish, if not enough with the android package installer to make this kind of "upgrade rom" or would do lack a proper "installer" (This I leave to the experts) ....
5. I guess that would make you need to restart the device or not, I do not know.
I think creating this "Linker", changing rom could be almost instantaneous and besides, I think both manufacturers and developers could be satisfied as to further develop roms without...............
Thank you very much and I await your expert opinion ... greetings !!