Related
i have cooked successfully more than 10 roms, WWE vesion to CHS vesion, they all work fine.
but when i want to cook a new rom based on LVSW 0320 vesion, i failed. i found that the default.hv can't be transfered to txt file, once i edit this file, os can't boot and stick on the SubSplash screen. but user.hv can do that.
sorry for post this new thread but i have posted under lvsw's thread and no one answer me.
can anyone help me plz, i really like this ROM.
thanks in advance.
i had the same problem... then i came up with a briliant solutiion
you know the user.hv and initdata can be edited without any probs..also this version of the rom deploys the ext rom aswell.. so what i did was i edited config.txt and added a cab with the HKLM etc regs that go into default.hv into the dump folder and generated a rom with that cab inside..
and VOILA... now i have a custom rom with all my settings... i figured this way out after hours of frustratingly trying to edit the default.hv
hope this helps
zohaer21 said:
i had the same problem... then i came up with a briliant solutiion
you know the user.hv and initdata can be edited without any probs..also this version of the rom deploys the ext rom aswell.. so what i did was i edited config.txt and added a cab with the HKLM etc regs that go into default.hv into the dump folder and generated a rom with that cab inside..
and VOILA... now i have a custom rom with all my settings... i figured this way out after hours of frustratingly trying to edit the default.hv
hope this helps
Click to expand...
Click to collapse
thank u, i have tried ur solution, but there is a big problem, .cab file doesn't support chinese caracter, so edit default.hv is the only way.
dont know if this would help you but take a lot here :
www.asukal.jp/hv_rom/hive2.txt
or simply use Make_HV, found it in the development & hacking thread.
First covert the hv file to rgu (which is simply REGEDIT4 Format) then make changes and convert it back.
qooqoo said:
i found that the default.hv can't be transfered to txt file, once i edit this file, os can't boot and stick on the SubSplash screen. but user.hv can do that.
Click to expand...
Click to collapse
This is my little surprise
qooqoo said:
thank u, i have tried ur solution, but there is a big problem, .cab file doesn't support chinese caracter, so edit default.hv is the only way.
Click to expand...
Click to collapse
You don't need a .cab for this. The program that goes through Config.txt can handle XML files with registry settings directly. So, grab any of the .xml files listed in Config.txt as a template for your own .xml file. Then just add your new .xml file plus a line in Config.txt referencing this new file, and you're all set.
There's another solution which I found much more convenient: use bepe's Rom Kitchen, and import whatever ROM you want. If I'm not mistaken, it's even available bundled with a Chinese ROM already. There you can edit the .rgu files from which the Registry will be created. This eliminates the need to read any of the .hv files. Worked very well for me! Also, since bepe's kitchen recreates the packet structure of the ROM, it's so much easier to understand which files and registry entries have a dependency or belong together. Highly recommended!
Cheers
Daniel
lvsw said:
This is my little surprise
Click to expand...
Click to collapse
weird suprise
lvsw said:
This is my little surprise
Click to expand...
Click to collapse
Why would that be a surprise? Is there more to this than meets the eye?
dutty said:
weird suprise
Click to expand...
Click to collapse
Indeed, I've been hitting my head against it for some days now...
lvsw said:
This is my little surprise
Click to expand...
Click to collapse
himan，give us a solution plz, it is a so good rom, but i can't add anything i want.
tadzio said:
grab any of the .xml files listed in Config.txt as a template for your own .xml file. Then just add your new .xml file plus a line in Config.txt referencing this new file, and you're all set.
Click to expand...
Click to collapse
thk u but i don't know how to edit a xml file, any suggestion?
tadzio said:
There's another solution which I found much more convenient: use bepe's Rom Kitchen, and import whatever ROM you want.
Click to expand...
Click to collapse
it is for CHT but not for CHS, there is a lot of CHT roms yet, cooked or offcial, but there isn't a official rom in CHS, a just want to convert 0320 vesion to CHS vesion.
I will be watching this thread.
Waiting for good news.
qooqoo said:
i have cooked successfully more than 10 roms, WWE vesion to CHS vesion, they all work fine.
but when i want to cook a new rom based on LVSW 0320 vesion, i failed. i found that the default.hv can't be transfered to txt file, once i edit this file, os can't boot and stick on the SubSplash screen. but user.hv can do that.
sorry for post this new thread but i have posted under lvsw's thread and no one answer me.
can anyone help me plz, i really like this ROM.
thanks in advance.
Click to expand...
Click to collapse
I have the same problem...the LVSW 0313 version was fine...then the new LVSW 0320 won't boot..stopped at the subsplash screen...it is strange that the default.hv is there but doesn't seem to booting the file.
qooqoo said:
thk u but i don't know how to edit a xml file, any suggestion?
Click to expand...
Click to collapse
Any Unicode-capable editor will do. Personally, I use UltraEdit.
Cheers
Daniel
Please don't take offense, but I'm starting to think you got the ROM as it is..."protected" that's why all the customizations are done via AutoRun.exe and xml files.
i found that lvsw 0325 edition can be edit.
qooqoo said:
i found that lvsw 0325 edition can be edit.
Click to expand...
Click to collapse
Yes, 0320 can't be edited. But 0325 could. But you can't use the regular tools..you have to use the "more Storage" tool, then just manually copy the "default.hv" and "user.hv" from the "dump" folder, use the regular tool and covert it to .reg. Then you make modifications to the registry file, convert it back to .hv and copy them back to the "dump" folder..you can add files by just copying files into the "dump" folder..after you are all done with it, just continue with the "more storage" tool to make your new-os.nb
I've been reading an gathering information for weeks now to build my own personal ROM. Since I'm unable (at the moment) to build one from scratch
Somehow it doesn't seem to work for me and I could not find an answer to my problems. I really hope some ROM Guru is willingly to help me out here.
I've used the Diamond Kitchen to extract the NBH files. And like it should it creates the OEM and SYS folders when you don't use protected ROM's like Dutty's, Swtos or Bepe's.
I've tried multiple ROM's to rebuild for my personal needs. And here are the most common problems I've encountered:
- Diamond (or Raphael) Volume Control does work. Even when it's included correct in the ROM. Reinstalling Volume Control after flasing using a CAB does work strange enough.
- The sound settings panel won't close after changing sounds.
ROM's I've tried to personalize:
- Panosha
- TOR (SubZero)
- SwiftBL
- VIC Lite
- And probably a few other ROM's I managed to extract (using the kitchen).
I've read some threads about the same problems but they seem to be part of a ROM thread instead of a specific "cooking thread". That's why I started it here.
Do you experience the same problems or do you have some good ideas than please let the rest of us know
I have the same problem
Everything seems OK, except the damned sound configuration.
If someone has an answer, we would appreciate it very much.
Thanks in advance...
Thanks for you reaction. Concerning the Volume Control, there is a way to get this to work. Just add a CAB that you call using the config.txt.
It's not ideal but it should work.
Unfortunately this procedure can't be repeated for the sound setting panel
I played with it a lot and even if I do nothing with the ROM, this sound config problem occurs. I extract the ROM and then rebuild it without modifying anything. This looks like a kitchen problem I thought.
I use Surface Kitchen v1.01. You another one, so this is a little confusing
Edit:
Maybe we can do the same without using those settings but direct in the registry?
Someone knows those keys?
Been using Kitchen 1.0.1 for a couple of days now as well. Updated the programs that were out of date. Did not help.
I also get always this error, could it be the cause?
iXiR said:
I also get always this error, could it be the cause?
Click to expand...
Click to collapse
HI iXiR
I also get the same error every time. I can not even cook the packages made with package creator. Some times I succeed but at the end it saye User.hv / custom.hv not found. Any idea?
thanks
tararura said:
HI iXiR
I also get the same error every time. I can not even cook the packages made with package creator. Some times I succeed but at the end it saye User.hv / custom.hv not found. Any idea?
thanks
Click to expand...
Click to collapse
Well, most of the times this fault is there, its a mistake with your new or edited rgu file like \\ or forgotten empty last row.
regards
Anja31
I recommend you guys try cooking the 1.93 official ROM .., i cooked a personal one for me .. no problems at all
iXiR said:
I also get always this error, could it be the cause?
Click to expand...
Click to collapse
this error is because you also have xip directory already listed in ur kitchen, so when the operation reaches that part of extracting the xip it dumps the xip and .dsm a.rgus, so basically a duplicate I dont use this kitchen but you can always press y to overite all
- The sound settings panel won't close after changing sounds.
Click to expand...
Click to collapse
Try adding this one to your registery:
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\LSOMACORE]
"Dll"="LsOmaCore.dll"
"Prefix"="DRM"
"Index"=dword:00000001
reset and you will be able to change the ringtone/press ok on your sound settings
To make it work while cooking, just place this in a RGU file so it will be implemented in the ROM
Thanks will try that one as soon as I can.
Had one crazy thought. Since there are some replies from some real cookers here I was wondering about the next thing.
At the moment I always select option "1" in my kitchen. So I don't rebuild it (option "2"). It shouldn't but is it possible to have more success when using option "2"?
I tried all variants....
select 1 (yes) -> Access denied
select 2 (no) -> the message will appear for a lot of files... even when you always select 2 the ringtone panel won´t work
select 3 (all) -> access denied
So IMO it has no impact, which option you take...
I choose "1". I just want to cook the ROM.
Ah.. now I understand what you mean... the question at the beginning...
of course you have to select "1"...
I talked about the overwriting question (screenshots in post before)
First of all: thanks for this thread...I was going crazy with this issue..!
Has anyone tryied the reg.key posted before?
PS: @maccune...did you tryied to recook swiftbl?! How?! Is it not a protected rom??
Might be wrong about SwiftBL. Tried so many that I could be mixing them up
Tried so many because I hoped there would be one that would work just fine.
If it was up to me I'd use TOR v5 since it's basic and still a Diamond build.
Also the cooker told he didn't mind if people would use his ROM as a base ROM for your kitchen
duttythroy said:
this error is because you also have xip directory already listed in ur kitchen, so when the operation reaches that part of extracting the xip it dumps the xip and .dsm a.rgus, so basically a duplicate I dont use this kitchen but you can always press y to overite all
Click to expand...
Click to collapse
Hi dutty, what do you use to cook and protect your rom ? a made home version ?
Sorry, wrong thread...
Caspertje19 said:
Try adding this one to your registery:
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\LSOMACORE]
"Dll"="LsOmaCore.dll"
"Prefix"="DRM"
"Index"=dword:00000001
reset and you will be able to change the ringtone/press ok on your sound settings
To make it work while cooking, just place this in a RGU file so it will be implemented in the ROM
Click to expand...
Click to collapse
Wohoooooooo!
It works... really great... perfect...
I also was going crazy to this issue....
now its solved.....
thx a lot.....
BUT: Another question: How can I add this as RGU File to ROM?
So, I set up my own kitchen based on the EasyPortOven and Bepes last WM6.1 Kitchen, added newer BuildOS and use it now with the Build 21215 SYS of xperia x1 with QVGA files and XIP of a Kaiser.
My problem is, that everything runs fine, until it comes to the point where it starts buildxip.
I just don't understand it.
Maybe somebody could have a look on it?
Here is the link:
http://www.4shared.com/file/103415760/304c8459/Kitchen.html
ice8lue said:
When I'm trying to cook my ROM using BuildOS, everything works fine, but the it shows an error, last status "Creating shadow order file..."
How can I fix this?
I updated BuildOS to v4.2b3 and it works but, after G'Reloc-ing I also get an Error about RadioButton1... ???
Click to expand...
Click to collapse
Solution for Error about RadioButton1...
Make sure you have a Create_ROM_for_Hermes.bat inside your 'Tools' Folder...
User Search menu (upper right) and look for Ervius Kitchen batch files... or
use ivan's or josh's kitchen tools...
OK, this is working now. Now Portxip.exe is crashing -.-
Tools Folder
Remove your tools folder and replace it with this one...
link
and Add this folder to your kitchen to... this folder is where the image of your New ROM will be created...link2
G'Reloc says I/O error 105 -.-
oh man this is annoying xD
thx for your help bro =)
I just don't get it, buildxip is crashing all the time...
I'll upload my kitchen here, maybe you could have a look on it?
try to replace your xip... or your OS.nb.payload
i've downloaded your kitchen and seems that there are too many problems ...
Try reading this first... especially the part wherein you need to study RAM allocation ...
SuperJustKitchen v0.9 Released.
Go to my site: http://justkitchen.info to get the updates and the info. It takes to long to update every device's forum that is supported, and I plan to support all devices, eventually.
Word of warning:
Not all EXT's have been tested or modified for the every device. Please test test and test and then let me know which packages don't work and what YOU've done to fix them. (I don't have time to fix ALL of them by myself.) Some packages will only be compatible with some devices.
(I'm no longer updating each thread separately for each device but just updating my site and posting the release info here. I will only update each thread to say that a new version is out.)
**Warning**
Before using this kitchen, you MUST read the whole thread. Any questions that have been answered will be ignored. This is your only warning.
**Disclaimer**
I am not responsible for any damage that may be done to your phone with a ROM created in this kitchen.
I am not responsible for any damage done to your computer.
I am not responsible for anything... at all.
Introducing SuperJustKitchen!
SuperJustKitchen is based on [http://forum.xda-developers.com/member.php?u=843218"]airxtreme[/URL]'s osKitchen Zero. All credit on for the kitchen backend goes to him.
Features
A completely stripped ROM. (Work in progress for some devices.)
LZX and XPR compression (Also option for No compression.)
Auto clean files that are language specific or DPI specific that your ROM does not need
Auto port missing language MUI files
Automatic rec'loc'ing for devices without native 6.5 nk's
6.1 and 6.5 support
Auto XIP and SYS porting
Auto NBH packing
Tool to convert OEM packages to EXT packages
Auto file conflict fix (don't have to removing older file that conflict (not that there are any. )
Save custom ROM settings (for cooks for multiple ROMs)
Cook multiple languages at the same time with the same ROM settings (Have to add language support yourself. I removed the required MUI's a while back because they made updating the kitchen and adding devices a nightmare.)
MUCH better organization of EXT packages
Active development instead of a program that is no longer being developed
Cleaner and easier to use interface
A built-in and customizable Tutorial section
And more!
Builds included
21056 - WM6.1
23658 - WM6.5 with new redesigned GUI
At the moment, this is an ENGLISH (WWE) only kitchen. This might change...
NOTE: In order for me to keep track of whether my time was well spent or wasted, if you use this kitchen to make a ROM, please either include SJK in the name or just mention that it was SJK cooked in your ROM's thread.
NOTE: This kitchen assumes that you know how to flash through SD, recover from a bad flash and are able to backtrack your steps to figure out how you broke your own ROM. If you do not understand these, please learn them first. Do not PM me asking me. I have written numerous walkthroughs on all these except on how to backtrack your steps. For that, just remember what you're doing as you do it and keep backups.
If you find any issues, PLEASE report them to the bug tracker in my website. It will help me make this kitchen better!
ENJOY!!!
woah,look who have we got here
thanks ivan
sir,this one is HOT DAMN!
i tried to cook a rom several times and i got particular error every time:
access to the path
....\build\sys\base_dpi_96_resh_240_resv_320\grass.jpg is denied
i tried to cook one with all sys packages and no ext packages and it didn't give me that error...
in my build i didn't include some "useless" packages and i added some of my own ext packages...which are correctly built out of sys packages and cabs (so i think it is not in the ext)
any help with this?
and one more thing...when you save a rom and try to open it...you get an error mentioning some value set to 0 or something like that
farukb said:
i tried to cook a rom several times and i got particular error every time:
access to the path
....\build\sys\base_dpi_96_resh_240_resv_320\grass.jpg is denied
i tried to cook one with all sys packages and no oems and it didn't give me that error...
in my build i didn't include some "useless" packages and i added some of my own oems...which are correctly built out of sys packages and cabs (so i think it is not in the oems)
any help with this?
and one more thing...when you save a rom and try to open it...you get an error mentioning some value set to 0 or something like that
Click to expand...
Click to collapse
Save your ROM configuration and upload it here. I haven't had the error you are having.
Sounds like a permission error on your computer. Strange.
both errors seem to be caused by net framework...it doesn't just seem so it says it is net framework...guess it's me and my pc.
but i still can't figure out how i don't get the access denied error when i put no ext packages
and sorry for misleading you...i mixed oem and ext in my second post because i was dealing with some oems at the time
so i did some testing
sys----ext----tweaks----changed pp----managed to cook
1------0--------0-------------0-------------1
*------0--------0-------------0-------------1
*------1--------0-------------0-------------1
*------1--------0-------------1-------------1
*------1--------**------------1-------------1
*menas partial sys (without useless packages)
**goes for tweaks enabled but with read-only mark removed from files in source folder
i didn't mention oem since i used all oems in every build
and i figured out that those files provided in sources were read only so when you enable tweaks which delete content you get a permission error
is it possible to make the delete option so that it only doesn't include those files in the build instead of deleting them
and a technical question....do those files need to be read-only...does it matter if you remove the read-only mark
farukb said:
both errors seem to be caused by net framework...it doesn't just seem so it says it is net framework...guess it's me and my pc.
Click to expand...
Click to collapse
You need to have .NET framework and C++ Redistributables.
farukb said:
but i still can't figure out how i don't get the access denied error when i put no ext packages
and sorry for misleading you...i mixed oem and ext in my second post because i was dealing with some oems at the time
Click to expand...
Click to collapse
Sorry, I don't understand your graph.
and a technical question....do those files need to be read-only...does it matter if you remove the read-only mark
Click to expand...
Click to collapse
Many of the files do have to be read only.
is it possible to make the delete option so that it only doesn't include those files in the build instead of deleting them
Click to expand...
Click to collapse
That is exactly what it's doing. It copies the files to a temporary folder first before it touches them.
ivanmmj said:
1.Sorry, I don't understand your graph.
2.That is exactly what it's doing. It copies the files to a temporary folder first before it touches them.
Click to expand...
Click to collapse
1....just a table of what i put in the build and what i did not,and did it work
2.yes,but it copies it with read-only mark and can't delete them
farukb said:
1....just a table of what i put in the build and what i did not,and did it work
2.yes,but it copies it with read-only mark and can't delete them
Click to expand...
Click to collapse
It copies things with read-only because the files have to be read-only for the ROM. What exactly are you trying to delete? (Does the kitchen function as I released it before your modifications/you trying to delete files?)
ivanmmj said:
It copies things with read-only because the files have to be read-only for the ROM. What exactly are you trying to delete? (Does the kitchen function as I released it before your modifications/you trying to delete files?)
Click to expand...
Click to collapse
it's about tweaks delete pictures and delete ringtones...as they come...
they don't perform their duty because they can't beat read-only
farukb said:
it's about tweaks delete pictures and delete ringtones...as they come...
they don't perform their duty because they can't beat read-only
Click to expand...
Click to collapse
Pictures and ringtones I can fix.
. NBH can do but cancel the 2% is not dry rum.
ipl/spl
1.12.0001
1.11.cmon
Update:
v0.8.1 - Fixed unflashable ROM bug
v0.8.2
Fixed LZX
Any chance for trinity ???
HI, can i use this kitchen fora an HTC trinity ? or can you provide the file needed????
morry70 said:
HI, can i use this kitchen fora an HTC trinity ? or can you provide the file needed????
Click to expand...
Click to collapse
To use it with the trinity, you'd have to port it yourself unless I get some time to port Trinity support into it.
I was able to create a Artemis ROM with your kitchen but unfortunatly the SD card is not visible. I know that extra drivers are necessary to support SDHC but I´ve the same problem with a normal SD card.
Do you have any idea?
Problem found, my SD card has been damaged.
Ivanmmj,
in your packages the applications for the camera and quickGPS are part of the EXT packages. Including this packages for cooking result in an error message that is it not signed with a trusted certificate or one of its components cannot be found.
Do you have any idea what´s wrong?
The site http://justkitchen.info seems to be down at the moment. Does anybody know of any alternate site from where we can download this ?
Bump. 0.9 Released.
First thx for helping me
I was trying to port a XIP from Touch Cruise
Yet it cant even boot in the system [only suck at the screen with the red words at the bottom]
Any clear tutorial for me. Thank you
You cannot just use the XIP from another phone.
You must get the XIP split into OEMXIPKernel and MSXIPKernel so that you can combine the new MSXIP with your existing Trinity OEMXIP.
And most of the time you would need to use the new build's SYS packages that go along with that new MSXIP.
What kitchen are using? Ervius Visual Kitchen?
the.decoy said:
You cannot just use the XIP from another phone.
You must get the XIP split into OEMXIPKernel and MSXIPKernel so that you can combine the new MSXIP with your existing Trinity OEMXIP.
And most of the time you would need to use the new build's SYS packages that go along with that new MSXIP.
What kitchen are using? Ervius Visual Kitchen?
Click to expand...
Click to collapse
Yes i am using Ervius Visual Kitchen
What i do is using the xipporterex to port the xip.
I even tried to follow the bepe tutorial from darkforceteam with bepe kitchen.
Yet same error occured.
Would u mind giving me a clear step for making it workable?
thx
Sorry but I have always used pre-extracted XIP/SYS bundles from people like Da_G that I then put into my kitchen. So I am not sure I can give you a full step through for porting the TC xip/sys from scratch.
One thing about the OEMXIP though, whenever I have used xipporterex I usually discard the generated ROM\Trinity\NEWBUILD# and replace it with a copy of my existing ROM\Trinity\OLDBUILD# (I just rename the folder to the new build number). It is just the ported ROM\Shared\NEWBUILD# folder that you want.
Again, you are also using the SYS\NEWBUILD# folder aren't you?
the.decoy said:
Sorry but I have always used pre-extracted XIP/SYS bundles from people like Da_G that I then put into my kitchen. So I am not sure I can give you a full step through for porting the TC xip/sys from scratch.
One thing about the OEMXIP though, whenever I have used xipporterex I usually discard the generated ROM\Trinity\NEWBUILD# and replace it with a copy of my existing ROM\Trinity\OLDBUILD# (I just rename the folder to the new build number). It is just the ported ROM\Shared\NEWBUILD# folder that you want.
Again, you are also using the SYS\NEWBUILD# folder aren't you?
Click to expand...
Click to collapse
Oh man! You are genius!!!
My rom comes bootable after renaming the folder!
That's so fantastic
Yet the xip of the system seems hasn't update [still the old build ]
Update
I used the old Build.. therefore, my device is bootable....
Yet when i choose back the new build, ext xip and sys as the neew version,
it suck again at the screen...
Thx man i know u have tried a lot to figure out my problem.
Is it possible or better, if i upload my kitchen for u to check?
OPzero said:
Oh man! You are genius!!!
My rom comes bootable after renaming the folder!
That's so fantastic
Yet the xip of the system seems hasn't update [still the old build ]
Click to expand...
Click to collapse
Oh thats easy. The "Rom Version" (that shows on boot) just needs to be patched (it is reading it from the copied OEMXIP).
Just go back into the Porting window then click the button "Find Date/Version on \ROM\Xip\"
That will populate the Rom Date and Rom Version fields.
You can then edit those fields and click each of the "Change" buttons to patch the newer Date/Version into the OEMXIP
You can also set the PagePool value using the "Change PP to Mb" function (it is not possible to query the current PP value however it does tell you what it previously was when you change it). You could always set it to something sensible like 4 or 6 and see what it was before that.
EDIT: If you were actually talking about the CE OS build number that shows in "About Device" then that is much harder to change. It is embedded somewhere within the MSXIP (requires hex editing I am not familiar with - and that is effectively make a "fake" build anyway).
OPzero said:
Update
I used the old Build.. therefore, my device is bootable....
Yet when i choose back the new build, ext xip and sys as the neew version,
it suck again at the screen...
Thx man i know u have tried a lot to figure out my problem.
Is it possible or better, if i upload my kitchen for u to check?
Click to expand...
Click to collapse
Oh, sorry just saw this ... yeah probably better to just do that.
Just curious but why on earth do you want to port some old TC 6.1 rom anyway?
There a plenty of functional WM6.5 xip/sys bundles that we can/have ported to Trinity. Even if it has be WM6.1 there are surely newer releases of 6.1 xip/sys to choose from?
EDIT: Just a heads up but I am about to go offline for the night (end of the work day in my timezone) so if you do upload I will not reply until tomorrow.
the.decoy said:
Oh, sorry just saw this ... yeah probably better to just do that.
Just curious but why on earth do you want to port some old TC 6.1 rom anyway?
There a plenty of functional WM6.5 xip/sys bundles that we can/have ported to Trinity. Even if it has be WM6.1 there are surely newer releases of 6.1 xip/sys to choose from?
EDIT: Just a heads up but I am about to go offline for the night (end of the work day in my timezone) so if you do upload I will not reply until tomorrow.
Click to expand...
Click to collapse
It's ok, would u mind pm or post some link which release those stuff?
Thank you very much!
I will still upload my rom and pm to u~
Check it when u hav time
really really thx
You could extract the 23102 wm6.5 build from my last kitchen release:
http://forum.xda-developers.com/showthread.php?p=5547181#post5547181
I have modified EVK slightly to allow it to build either p3600i or Trinity ROMs from the same kitchen but still there is a full QVGA xip/sys bundle there for 23102 (give or take a few sys packages).
Got to go, will try and be more helpful tomorrow
the.decoy said:
You could extract the 23102 wm6.5 build from my last kitchen release:
http://forum.xda-developers.com/showthread.php?p=5547181#post5547181
I have modified EVK slightly to allow it to build either p3600i or Trinity ROMs from the same kitchen but still there is a full QVGA xip/sys bundle there for 23102 (give or take a few sys packages).
Got to go, will try and be more helpful tomorrow
Click to expand...
Click to collapse
Yes I got it~ Thx
it is great
OK and now i am going to mod it~~
Yet just before i start, would u like suggesting me some post that is most updated and clear enough for me such a newbie to work around it?
Thx
OPzero said:
Yes I got it~ Thx
it is great
OK and now i am going to mod it~~
Yet just before i start, would u like suggesting me some post that is most updated and clear enough for me such a newbie to work around it?
Thx
Click to expand...
Click to collapse
Go and find SuperSport's Tutorial Video for using Ervius Kitchen.
I have broken up the EXT packages into categories to make it simpler for new chefs but the basic concept is the same.
I have included pre-built ROM profiles to make it very simple to build ROMs out-of-the-box.
Just got to "Load ROM", choose one for your phone (P3600i or Trinity) and the click "Create ROM" to build it.
Load a few different profiles and look at what changes in the settings. That should help you see what is going on.
Check out this thread for more tutorials and guides:
http://forum.xda-developers.com/showthread.php?t=669414
the.decoy said:
Go and find SuperSport's Tutorial Video for using Ervius Kitchen.
I have broken up the EXT packages into categories to make it simpler for new chefs but the basic concept is the same.
I have included pre-built ROM profiles to make it very simple to build ROMs out-of-the-box.
Just got to "Load ROM", choose one for your phone (P3600i or Trinity) and the click "Create ROM" to build it.
Load a few different profiles and look at what changes in the settings. That should help you see what is going on.
Check out this thread for more tutorials and guides:
http://forum.xda-developers.com/showthread.php?t=669414
Click to expand...
Click to collapse
1 more question
I downloaded a XIP SYS Pack from
http://forum.xda-developers.com/showthread.php?t=650783
However there are 5 Folders
How can i port them into the kitchen?
Thx for that
OK, this technically requires more time than I can spare to explain thoroughly ... but maybe if I just outline the steps you can do some google searching to work out exactly how to do it:
- First you need to clean up the SYS for you needs. For Trinity you need to have QVGA sys structure so that means only 96DPI and 320x240
- That means sorting the SYS package folders into an EVK SYS structure and removing the other DPI and resolution folder structures.
- Go get XIPDumpSoter (or whatever it is called now) by teh penguin so that you can use it to automatically sort the folders. Then delete any that are for other DPI or RES (eg: 192DPI or 640x480, etc). You _only_ want 96DPI and 320x240 (and of course any that are non-res specific)
- That should give you the folder structure to put into \SYS\NEWBUILD#\
- You will need to copy over the WINCENLS sys package from your existing SYS as that will not be in the new SYS (there are other replacement folders like SQM_DUMMY, and also some that we often just delete but you can learn that stuff later)
- We have already discussed what you need to do with the MSXIP
- Lastly, (and this is really very much the "art vs sicence" part), you will need to go through and "recmod" a certain number of "modules" within certain sys packages.
I simply don't have the time right now to get into recmod but if you google you will find plenty of helpful posts explaining it. I think there is even a basic recipe of what to recmod for 64M users done by JooJooBee ... that would get you going.
Put simply, at this stage you need to read read read read read lots of chef threads to pick up the finer details. Sorry I am too busy at work to be any more help than this.
Good luck.
Thank you for spending time on me
I know it is rather annoying to explain a few things
Really Really Thank you for helping me
I hope that my post could be a guide for others
Update:
The rom is still unbootable after a day of trying.
Does the OEM section be edit before updating the build?
Such as initflashfiles.dat [I read the in the tutorial that it should change to the native 6.5]
May be i started from the wrong step?
What i concern is that wm6 may not suitable to update directly to wm6.1 or wm6.5
Thank you for spending much time on helping me
If it can be google, simply give me the keyword,
I will finish the entiry
And finally, thank you!!
OPzero said:
Thank you for spending time on me
I know it is rather annoying to explain a few things
Really Really Thank you for helping me
I hope that my post could be a guide for others
Update:
The rom is still unbootable after a day of trying.
Does the OEM section be edit before updating the build?
Such as initflashfiles.dat [I read the in the tutorial that it should change to the native 6.5]
May be i started from the wrong step?
What i concern is that wm6 may not suitable to update directly to wm6.1 or wm6.5
Thank you for spending much time on helping me
If it can be google, simply give me the keyword,
I will finish the entiry
And finally, thank you!!
Click to expand...
Click to collapse
I'm actually going to bed before 3am tonight, so I will not be long here, but I just had a thought. When you cook the ROM, are you checking "Real WM 6.5 AKU" in the Kitchen? Don't do that. You cannot actually use a Native 6.5 Kernel on the Trinity as one does not exist. Also, as mentioned by the.Decoy before, you MUST have 'wince.nls' in your Kitchen somewhere or it will not boot. Thirdly, try cooking a version without ANY Extended packages. Only the original XIP and SYS and see if that boots. When you get that going smoothly, start adding EXT packages. Good Luck!
I'll check back in a couple days to see if you've made any progress. If you'd like to send your kitchen to me also, I'd be happy to look it over and see if I can find anything wrong in there.
Again and Again
I keep remind myself that Native 6.5 Kernel should be checked
OMG The Bug is here
And Thanks Decoy
Thank You
Thank You!!!!!!!!!!!!
================================
Update:
I saw a folder called 0_ROM_Version in EXT Shared
What is it and what function does it have?
Thx
OPzero said:
Does the OEM section be edit before updating the build?
Such as initflashfiles.dat [I read the in the tutorial that it should change to the native 6.5]
Click to expand...
Click to collapse
Ummm are you trying to use a freshly extracted OEM from an official ROM?
If so then yes, there is a massive amount of conversion that must be done to it before you an cook it into a rom. Even before you break it up in to components and edit all the reg and dat files ... you first need re-sign everything with an SDK cert because you won't have the official cert that HTC built them with.
Seriously. If you are just starting out then use an existing chef's OEM (use mine or anyone else who has posted a kitchen).
Even I have not yet ever had the time to complete build an OEM from scratch (not that I don't want to one day). I was always just adapting the OEM that Chanvi had provided us in his kitchen, primarily because he had already done all the work to make it mesh with WM6.5
OPzero said:
Again and Again
I keep remind myself that Native 6.5 Kernel should be checked
OMG The Bug is here
And Thanks Decoy
Thank You
Thank You!!!!!!!!!!!!
================================
Click to expand...
Click to collapse
I am bit confused by what you said there
As Supersport explained, we do not have a Native 6.5 kernel for Trinity.
So that option should not be checked.
OPzero said:
I saw a folder called 0_ROM_Version in EXT Shared
What is it and what function does it have?
Thx
Click to expand...
Click to collapse
Again, this is why I said to try "Load ROM" and see what happened
Those are just simply EXT packages which contain 1 single provxml. Each one sets the registry value for "ROM Version" (the info that comes up in "About Device" in Settings). There is one for every type of "Saved ROM" you can build from that kitchen.
I created them so that people could build each of the several types of rom from my kitchen but never need to edit the provxml files to change what the version info was.
If you are going to try cooking your own roms, the best advice I can give you is find a text editor you like and just start opening up ALL of the REG DAT RGU and PROVXML files you can find and see what they are doing.
You can even do it from within EVK. Select the type of file on the left panel called "Editors" (or just select "All") then click "Show Editor". You can open the files it finds by double clicking them in the panel on the right.
Anything custom that ever happens in the setup of a rom is controlled by these files.
If you want to see how something works (or what it does), just open up the files and read them
Sorry, wt i mean is that my rom become bootable after unchecking it
~~ That is so amazing ~~
Now i am Reading the horrible, endless.....etc tutorial, [I can finally have my own rom ]
1 Question, I am trying to put a new wince.nls which content much more countries in the rom. Yet it comes unbootable after i have repalced it.
I googled around and found several solutions.
1 is that i should put it in OEM rather than SYS [I havn't ried it yet i think it won't work]
2 is that i should mod the size of the xip.bin
Therefore it is big enough to store it.
3 Adding in some registry with my selected country code
Thanks for helping me ~~
Sorry can't help you there.
I have never ventured beyond WWE lang for my kitchens.
OPzero said:
1 Question, I am trying to put a new wince.nls which content much more countries in the rom. Yet it comes unbootable after i have repalced it.
I googled around and found several solutions.
1 is that i should put it in OEM rather than SYS [I havn't ried it yet i think it won't work]
2 is that i should mod the size of the xip.bin
Therefore it is big enough to store it.
3 Adding in some registry with my selected country code
Thanks for helping me ~~
Click to expand...
Click to collapse