Related
vivi ROM Kitchen for iPAQ Hx4700
Mainly modified from Scoter Kitchen
Introduction
I've made this iPAQ Hx4700 ROM Kitchen because I think someone can make it,but no one 've made it till now. So I made it myself and share.
And someone asks me for this after I publish my vivi ROM Kitchen for ASUS P525.
Though it is not the best and complex Kitchen with many features and I think not many users want this Kitchen,but it's good to share.
The main aim of this ROM Kitchen is easy using, so this ROM Kitchen is only one click and follow the screen.
You will have a new ROM for iPAQ Hx4700 at ease.
Aims
1.For easy modifying private ROM.
2.For helping new user to easy start cooking ROM.
3.For sharing OEM Packages.
4.For someone makes it better.
Let's see
Before using it just let us understand in the same way as follows.
1.This ROM Kitchen is made for using with iPAQ Hx4700 only,but it can be use with any other device if modified a little.
2.This ROM Kitchen is modified mainly from Scoter Kitchen.
3.The commands are modified from DoubleOFour ROM Kitchen , edhaas ROM Packer Kitchen and vivi ROM Kitchen for ASUS P525
Credits should give to them , not me.
Tools use
1.Tools in Scoter Kitchen included bepe package tools and mamaich tools.
2.xda3nbf tool(Don't know who made this tool).
Ingredients
There are 3 parts.
1.Program Part : The Kitchen itself
vivi.exe
2.ROM Part
3.OEM Part
Download
For WM6
NEW : vivi Kichen for Hx4700 New version
http://www.zshare.net/download/4800955976eec2/
Use kozhura WM6 OS 5.2.1933 Build 18533.0.7.0 as Base ROM
THANKSSS kozhura !!!!!
OLD : The Kitchen and Base ROM in executable file vivi.exe
for WM6 ROM
http://www.zshare.net/download/410370393f182d/
For WM5
for WM5 AKU3.5.2 ROM
http://www.zshare.net/download/416811401f517e/
2. OEM Packages
You can find OEM Packages or create your OEM Packages by looking at this thread.
http://forum.xda-developers.com/showthread.php?t=303195
If you don't add any OEM Packages , the new ROM created will be the same as kozhura ROM I use as Base ROM , since I didn't modify anything in kozhura ROM.Both WM5 and WM6 kozhura ROMs are great!!!
THANKSSS kozhura !!!!!
Base ROMs
Base ROMs are latest kozhura WM6 WWE ROM and kozhura WM5 AKU3.5.2 but repacked as Packages and modules.
Already included in each Kitchen for easy using.
Choose the right Kitchen!!!
How to cook
1. Place vivi.exe from download 1 in Root of C: and execute it.
You will see a new folder named vivi , this is your Kitchen.
2. Enter Kitchen
3. Place OEM Packages you choose in OEM folder.
4. Click Start.cmd.
5. Follow on screen.
That's all.
Note : Be sure to not add many OEM Packages because there is not much space left.
Thanks
@ Xda-developer.com
Thanks bepe for BuildOS.exe and Packages Tools.
Thanks mamaich for ROM Tools.
Thanks JKR for Scoter Kitchen.
Thanks DoubleOFour , edhaas for Kitchen I use as command guide.
Thanks kozhura for WM6 and WM5 AKU3.5.2 WWE ROMs as Base ROMs.
And thanks all my friends.
Tips
1.Before you Exit BuildOS,you can go to temp/dump and delete all rgu files and nearly all html files except these 9 files.
1.compose_mtgreq.htm
2.compose_note.htm
3.compose_sms.htm
4.compose_vcard_sms.htm
5.default.html
6.read_mtgreq.htm
7.read_note.htm
8.read_sms.htm
9.read_vcard_sms.htm
Or you can edit welcomehead.192.png or another files as you want.
Regards,
vivi
PS
1.I know there are many experts here.This is my attempt to help us, Hx4700 users, to make our devices better as best as I can.
2.I don't want any credits for this Kitchen , only named it vivi Kitchen since it is my attempt and only want to give this community back the thing I can do.Credits should go to the names I stated in Thanks Part above.
3.I hope you will develop this Kitchen better and share.Or share your OEM Packages or knowledges.
4.All feedbacks are welcome.
Thanksss
Vivi,
THANK YOUUUUU!!! I'd been trying to modify your ASUS kitchen with no success. The 4700 community will truly appreciate this. I agree, kozhura's rom is great.
Regards.
Thanks so much vivi! I'm so happy!
Is it possible for me to use kozhura's latest WM5 ROM as the base rom? What should I do to make that into packages and modules? Also, is there any way to calculate how much free space is left in the ROM for adding OEM packages?
Thanks again!
Thanks. This is giong to be my first "cooking" experience. A nice new way of playing around and improving the hx4700 at the same time!!
Been doing some late night cooking... tastes great. Thanks vivi for bringing this out.
Thanks for the WM5 kitchen!
bub181 said:
Thanks so much vivi! I'm so happy!
Is it possible for me to use kozhura's latest WM5 ROM as the base rom? What should I do to make that into packages and modules? Also, is there any way to calculate how much free space is left in the ROM for adding OEM packages?
Thanks again!
Click to expand...
Click to collapse
Vivi already stated in his post that the base rom is the latest kozhura WM6.
==========
Base ROMs
Already included in Kitchen for easy using.
Base ROM is latest kozhura WM6 WWE ROM fixed 2 but repacked as Packages and modules.
What should I modify to get a 8MB or 32 MB PagePool?
Thanks.
Vivi
Don't downplay your part here!
I'd had a tinker with decompiling the ROM but never quite got it to work right so I too am very grateful of your assistance here.
I had a quick play last night and the largest file I saw was Powerpoint, my old favourite for the largest waste of space on previous ROMs so first to go to make space for the useful stuff!
And just how can you remove Powerpoint?
pepeluu said:
And just how can you remove Powerpoint?
Click to expand...
Click to collapse
Well simply deleting the 2.59MB ppt.exe executable from the SYS\Office folder will get rid of it, but how do you get rid of all the traces (registry settings, links, extensions) that are tied to it in a clean and efficient manner. I know I can manually remove associated files and such, but what happens to settings in the .dsm file? I can manually edit the .rgu files, but how do you edit existing settings in the .dsm files without breaking something?
Can I remove the "HP Protect Tools" OEM folder (15836286-5263-4a11-8b33-5087ced93124) safely, or is it required by other applications in the ROM?
Casual User said:
Well simply deleting the 2.59MB ppt.exe executable from the SYS\Office folder will get rid of it, but how do you get rid of all the traces (registry settings, links, extensions) that are tied to it in a clean and efficient manner. I know I can manually remove associated files and such, but what happens to settings in the .dsm file? I can manually edit the .rgu files, but how do you edit existing settings in the .dsm files without breaking something?
Click to expand...
Click to collapse
And then, deleting ppt.exe will cause no harm, even if you leave there all the debris? 2.6MB gives quite a lot of room for small apps!
vivi Kitchen for Hx4700 WM5 AKU3.5.2 as requested.
http://www.zshare.net/download/416811401f517e/
details : http://forum.xda-developers.com/showpost.php?p=1570670&postcount=1
pepeluu said:
And just how can you remove Powerpoint?
Click to expand...
Click to collapse
I delete the ppt.exe as suggested, but I go through every file also to be honest and remove anything that refers to powerpoint, the link file, registry values for 'pps' or 'ppt'.
Whilst doing this I remove other things I don't use (though to be fair this is from when I used the Universal which had a lot of extra crap in it) and tweak the registry value to those I want (though again I can't see that I need to change a lot here).
Easier and quicker is to do a search of all files for the contents of ppt and pps and delete from there.
Vivi many thanks to you,great work for users!
kozhura,
Appreciated your works so much.
You are genius and so kind.
Thanksssssssssss,
vivi
Hi,
I have looked a litlle in your kitchen and this is a very useful tooll, thanks !!
Here are my first questions :
1.
I have seen this folder in the OEM :
vivi\Enter Kitchen\OEM\b693f6e6-e6cd-4091-b8f3-40f2b988b169
It seems to regroup every phone manager. As I never used it and I don't inted to use it, can I delet this 2.38 Mo folder without any risk ?
2.
Does someone have information about changing keyboard or adding a new one ?
(I need an azerty one)
3. (harder)
Does someone have information about changing language of the rom ???
4.
How much space do we realy have left to add OEM packages ? (I have searched but I didn't find an information about it)
albertorrent, I can't help you specifically but when I play with ROMs I tend to keep the last working version and then tweak.
If it works fine, that is the new last saved version, otherwise I go back to the previous and tweak differently.
thanks, I think I 'm gonna do a lot of try.
I have an other question, (may be the last for today ;-))
How to add a font in the font folder in windows ?
Hi all,
I've managed to find a dump of build 19900, however I haven't managed to make a working ROM out of it as yet. I'm hoping to find a way to get it working with bepe's kitchen tools - therefore removing the reliance on a custom chinese binary to build these ROMs.
I believe this ROM is big storage, so I'd like to make available a non big storage version as well for everyone to benefit.
Any takers to help out?
Download URL: http://rapidshare.com/files/113432995/Hermes_RomKitchen_19900.rar
CRCinAU said:
Hi all,
I've managed to find a dump of build 19900, however I haven't managed to make a working ROM out of it as yet. I'm hoping to find a way to get it working with bepe's kitchen tools - therefore removing the reliance on a custom chinese binary to build these ROMs.
I believe this ROM is big storage, so I'd like to make available a non big storage version as well for everyone to benefit.
Any takers to help out?
Download URL: http://rapidshare.com/files/113432995/Hermes_RomKitchen_19900.rar
Click to expand...
Click to collapse
Will take a look at it dude, aint got a load of time at the mo though. Might have a quick PM session and see if theres a WWE version we cna use.
Have you guys tried PM'ing Dvha79_ddt? I'm not much help on cooking but i'll try and suggest anything
Good luck guys.
Need testers let me know.
I've managed to get the ROM to build using Bepes kitchen, however it doesn't boot. It sits there at a black screen on power on...
This leads me to believe it's part of the XIP that is just wrong.
I've attached what I've extracted from the included os.nb by doing:
nbsplit -hermes os.nb
RomMaster -w 5 os.nb.payload -x -o xip.bin
Run xipport, choose Dump xip.bin
I then deleted os.nb & os.nb.extra.
Then put the XIP dump together as it should be (i think) for bepe's kitchens.
Not 100% sure where to go from here...
edit: Oh, I've attached the TOOLS directory too - just in case you don't have a copy of Bepes great work.
This is a non big storage modded 19900 xip that works.
I haven't used in a kitchen just yet.
I will have a look at the dump later on.
dan1967 said:
This is a non big storage modded 19900 xip that works.
I haven't used in a kitchen just yet.
I will have a look at the dump later on.
Click to expand...
Click to collapse
Hmmm - I've used your XIP - it boots, but same as using the default ROM kitchen tools, it hangs after displaying splash2. I replaced the OEM_FLASHDRV.DLL in OEMDrivers with a non-BS version, in case that was an issue, but still no go...
CRCinAU said:
Hmmm - I've used your XIP - it boots, but same as using the default ROM kitchen tools, it hangs after displaying splash2. I replaced the OEM_FLASHDRV.DLL in OEMDrivers with a non-BS version, in case that was an issue, but still no go...
Click to expand...
Click to collapse
For now you can try to merge that XIP with the payload from the ROM (without kitchen) and it should boot&work.
Will try to get the romhdr.bin and in fact to rebuild the whole ROM folder and let u know whats happening.
Using Dvha79_ddt 900
I know it's not what you are looking for, but I am using Dvha79_ddt ROM and it is working as well as his 701 which was very fast and rock solid. Would like to help in any way I can as I loved your ROM's apart from the issues. As a noobie where do you find these ROM's in the first place?
A lot of it is hit and miss finding things here and there - like this kitchen that seems to be almost complete, but just doesn't work. A bit of hacking around and it can probably be made to work.
As WM6.1 doesn't exist for the hermes devices, it is always ported from something else - which can lead to weirdness.
Most of it is pot luck, and a lot of knowledge (and I'm missing some in getting this kitchen working )
just a working trick
what I am sure is working (tried it before) is replace the whole ROM folder from new kitchen with your working one and then just slip in the xip.bin into the new payload in a few steps.
Still can't get this working....
I've changed the BuildNB.bat to show the following:
Code:
echo.
CD ROM
..\TOOLS\buildxip.exe -b
if not "%errorlevel%"=="0" goto error
del out.bin
copy xip_out.bin out.bin
CD..
This should use your XIP in the ROM, which shows as 3.62.07.Dan - however I still can't get past splash2... Eventually, the backlight goes out, but it doesn't seem to display anything past splash2... Eventually, the screen goes off (power setting). Turning it back on via the power button just gives me a white screen... I'm at a loss to figure out what's happening here.
The OS.nb.payload is the same (non-BS) that I was using from my 10.1 release of my ROM, and the XIP folder contains the same XIP as 10.1 release (Build 19209) - however the XIP version shouldn't matter, as we delete it and merge yours into the OS-new.nb instead...
About the same happened to me and after a re-flash of a good nbh I got some very strange things happening. I could not install any cab. Very weird.
I had to format everything.
Anyway the xip is working if slipped into old rom, but that's not much of a news...
I looked into S00 of FLASHDRV.DLL module in order to convert it, but it does not look like usually.
Maybe that dump is not from a hermes device.
Hrrrm - that is possible, however the site said that it was for Hermes devices... Are you looking at it in the OEMDrivers directory or the XIP?
Can we swap out the FLASHDRV.DLL from a working ROM? I'm pretty sure that isn't tied to a certain build?
CRCinAU said:
Hrrrm - that is possible, however the site said that it was for Hermes devices... Are you looking at it in the OEMDrivers directory or the XIP?
Can we swap out the FLASHDRV.DLL from a working ROM? I'm pretty sure that isn't tied to a certain build?
Click to expand...
Click to collapse
I can try to make it work with the XIP from the 19900 version existing on this thread. (actually from there was the xip I uploaded). Could it work? There will be maybe a 409 & 804 conflict?? I have no clue really. Can only try.
I don't believe the XIP is localised, nor are the OEMDrivers. I may be wrong here though. 409 vs 804 should in theory only become an issue when applications that use localisation is involved..
It is definitely not a hermes rom as the kitchen does not accept a hermes payload while other kitchens accept older (different) payloads. Kitchen halts at ImgfsFromNb.
I can not think of something else. I give up on this one.
Hrrrmmm...
What about this:
ftp://user:[email protected]:333/Aikon/Build19900RKXiaoQiao.7z
It weighs in at 145Mb, but it is supposed to be another Hermes 19900 kitchen that I haven't managed to get going either...
The XIP definatly isnt localised at all,
What sort of sizes are you guys getting for the os.nb filesize?
CRCinAU said:
Hrrrmmm...
What about this:
ftp://user:[email protected]:333/Aikon/Build19900RKXiaoQiao.7z
It weighs in at 145Mb, but it is supposed to be another Hermes 19900 kitchen that I haven't managed to get going either...
Click to expand...
Click to collapse
The download speed is obscene. It will finish maybe tomorrow.
Hi every gurus and chefs,
Thanks to creators of kitchens and tools, i have had so much fun in cooking my own rom. Thank you so much.
Recently, i tried to convert the 1.93.456.2 WWE ROM to CHS. I have managed to transform 99% of the ROM into CHS. but there is only one problem. When creating the rom using the diamond kitchen or kaiser kitchen, at the ending part, it will fall back to use os.nb within the ROM\ folder.
From my understanding, the OS.NB file is an extracted OS from the original WWE ROM thus, the boot.hv, boot.rgu and wince.nls is still the WWE version. how do I replace these files?
Another question would be, when dumping the official rom, the dump_XIP folder is created. what is the use of this folder? if i make changes to the folder, how to i merge them into a usable part for cooking?
i have did a lot of reading on XIP porting, big storage rom cooking and etc. i just can't seems to locate one which explains how to replace files in os.nb or merging the XIP folder to usable part.
Can any kind soul please kindly advise?
Thanks you so much!
You may want to have a look at ababrekars SYS and XIP porting guide in Elf section....
ruffruff said:
Hi every gurus and chefs,
Thanks to creators of kitchens and tools, i have had so much fun in cooking my own rom. Thank you so much.
Recently, i tried to convert the 1.93.456.2 WWE ROM to CHS. I have managed to transform 99% of the ROM into CHS. but there is only one problem. When creating the rom using the diamond kitchen or kaiser kitchen, at the ending part, it will fall back to use os.nb within the ROM\ folder.
From my understanding, the OS.NB file is an extracted OS from the original WWE ROM thus, the boot.hv, boot.rgu and wince.nls is still the WWE version. how do I replace these files?
Another question would be, when dumping the official rom, the dump_XIP folder is created. what is the use of this folder? if i make changes to the folder, how to i merge them into a usable part for cooking?
i have did a lot of reading on XIP porting, big storage rom cooking and etc. i just can't seems to locate one which explains how to replace files in os.nb or merging the XIP folder to usable part.
Can any kind soul please kindly advise?
Thanks you so much!
Click to expand...
Click to collapse
Hi,
1. You don't have to replace/port XIP from the ROM of the same device. Only do this if you want to port other devices' ROMs such as Kaiser to Hermes, Diamond to Kaiser, Raphael to Diamond etc. It will boot.
2. Just replace the wince.nls version in the SYS\WINCENLS_WWE with the CHS one you have.
3. Modify all the MUI files and registry as to point to your Language of choice.
4. The OS.NB is needed as the shell/container for your new cooked ROM because it's the requirement for using the Tadzio's tools. So, leave it as is.
5. Cook the ROM.
At least that what I did when doing my Hermes version long before.
Cyphol.
ruffruff said:
Hi every gurus and chefs,
Thanks to creators of kitchens and tools, i have had so much fun in cooking my own rom. Thank you so much.
Recently, i tried to convert the 1.93.456.2 WWE ROM to CHS. I have managed to transform 99% of the ROM into CHS. but there is only one problem. When creating the rom using the diamond kitchen or kaiser kitchen, at the ending part, it will fall back to use os.nb within the ROM\ folder.
From my understanding, the OS.NB file is an extracted OS from the original WWE ROM thus, the boot.hv, boot.rgu and wince.nls is still the WWE version. how do I replace these files?
Another question would be, when dumping the official rom, the dump_XIP folder is created. what is the use of this folder? if i make changes to the folder, how to i merge them into a usable part for cooking?
i have did a lot of reading on XIP porting, big storage rom cooking and etc. i just can't seems to locate one which explains how to replace files in os.nb or merging the XIP folder to usable part.
Can any kind soul please kindly advise?
Thanks you so much!
Click to expand...
Click to collapse
please correct me if i was wrong..
afaik, XIP part is the same for every language,
also in the end part of the building, you need os.nb only as a "template" to rebuild the new one... it wasn't really use the content inside...
normally, you need to copy all content in the dump_xip to the ROM\XIP directory...
to learn about the process of diamond kitchen (which is based on kaiser kitchen so i assume the tools are the same), i think you better use the kaiser ROM, and try to dump it.. and see what directories and files are generated...
in kaiser kitchen, to rebuild the rom you need 3 dirs, OEM, SYS, and ROM\XIP
cyphol said:
Hi,
1. You don't have to replace/port XIP from the ROM of the same device. Only do this if you want to port other devices' ROMs such as Kaiser to Hermes, Diamond to Kaiser, Raphael to Diamond etc. It will boot.
Click to expand...
Click to collapse
He would need to if he wants a different OS build. Or am I wrong?
pkoper said:
He would need to if he wants a different OS build. Or am I wrong?
Click to expand...
Click to collapse
of course....
pkoper said:
He would need to if he wants a different OS build. Or am I wrong?
Click to expand...
Click to collapse
Yes, that's right for the reason. If that's the only reason, why don't you replace the core.dll
thank you everyone for your advise.
looks like i just need more reading.
thank you cyphol, pkoper and teamee for your kind advice.
I have replace the SYS\wincenls_WWE folder with SYS\WINCENLS_0804. i believe this might be one of the problems. i will try replacing just the wince.nls within the folder instead of replacing the entire folder.
files which i have modified includes the boot.hv, user.hv, default.hv, boot.rgu, a bunch of other rgu as well. i might have missed out a few others. so i will check again.
thanks everyone for your kind advice. if there is any other suggestions or points to take note of, please kindly let me know.
your guys rocks! XDA rocks!
Trying to cook a rom & i need a base clean rom for trinity with the last build
can somebody help me with that or tell me how to get a base ROM
Thanks
read the sticky threads in this forum
get a kitchen and upgrade the rom from the kitchen with the xip, sys you want
Thanks
but which files inside the SYS folder should i replace to update the build and make a clean rom with minimum size for future cooking??
are they the folders of dll files or OEM or what??
start reading the forum
try this
get a clean sys, replace in kitchen and do relocating with g'reloc as described in the thread
All,
I own an MwG (formerly ubiquio) 501 and eventually started looking for software updates for it. The device is mostly ditto to the imate JAQ3, so I proceeded as follows:
1- get a WM6.1 ROM for JAQ3 (as linked in a thread of this very forum)
2- try to flash it (fail)
3- disassemble the ROM with tools from chinese website (osnbtool.exe)
4- port XIP merging with the ROM of my own device (thanks to the wonderful manual full xip porting thread!)
5- insert my original IMGFS of SYS and OEM
6- success!
the current situation is (settings -> about)
CE OS 5.2.20269 (Build 17936.0.3.0)
The performance boost obtained by upgrading the XIP is significant (keyboard is usable and video playback is ~ 15fps @ full screen), but I would like to perform more optimizations (e.g. switch to .NET CF 3.5) but as soon as I start to work with the dumped SYS and OEM I have troubles, it seems that every kitchen is expecting to work on the XIP (or on .nb and .nb.payload) but such files are not compatible with the one I get from osbntool.exe (but the dump folder is).
Do someone have advice on how to proceed? I would like to either
1-find a kitchen that works with my device
2-go for manual cooking
For 2 I achieved to split the dumped folder to packages and removed some of them, then - as far as I understood - I would need Greloc (got it) and bepe's buildos.exe (nowere to be found )
Is someone willing to help me? Thanks a lot.
Rest assured I am going to share the obtained ROM (I am already willing to share the current one, of course, just drop me a line!)
Best,
DAniele