Related
Someone please help me on getting the blackberry connect to work.
aih1977 said:
Someone please help me on getting the blackberry connect to work.
Click to expand...
Click to collapse
you need to hex edit the build number to get it to work...
how do i know what hex to do. i found old trends but it didnt work can you please explain to me how or what to do thanks
got it...at first glance thought there was a bbconnect 3.30.0.9 version...No it is lvsw rom version...
aih1977 said:
how do i know what hex to do. i found old trends but it didnt work can you please explain to me how or what to do thanks
Click to expand...
Click to collapse
A good place to start if you are serious about it - this thread. I can't afford to do this myself, as I need my phone 24x7.
moisha said:
A good place to start if you are serious about it - this thread. I can't afford to do this myself, as I need my phone 24x7.
Click to expand...
Click to collapse
I went there and it is no help. I need to do this ASAP so one please tell me what hex to edit in detail because i am not to talent in programing thanks
aih1977 said:
I went there and it is no help. I need to do this ASAP so one please tell me what hex to edit in detail because i am not to talent in programing thanks
Click to expand...
Click to collapse
You need to use nbhextract to get the OS.nb file from the nbh... then open the OS.nb file in a HEX editor... Search for the appropriate version string and change it in HEX....
ok this is how to do this.
you need to first extract the kernel from the OS.nb
The kernel is in the XIP section, not IMGFS of the rom.
To obtain the XIP section, use rommaster.exe and dumpromx.exe
once you have obtained coredll.dll (the kernel) then Open that up with a HEX editor and search for the current KERNEL (CE) number.
Onc eyou have obtained the current CE number you then have to replace that HEX string with the 5.1.195 HEX string by editing the OS.nb.
Done.
P.S: dont ask me for the 5.2.1236 HEX string as I dont know it, my roms are based on a newer kernel than those in custel and LVSW's roms.
walshieau said:
You need to use nbhextract to get the OS.nb file from the nbh... then open the OS.nb file in a HEX editor... Search for the appropriate version string and change it in HEX....
Click to expand...
Click to collapse
how do i find the string and what do i change too
jasjamming said:
ok this is how to do this.
you need to first extract the kernel from the OS.nb
The kernel is in the XIP section, not IMGFS of the rom.
To obtain the XIP section, use rommaster.exe and dumpromx.exe
once you have obtained coredll.dll (the kernel) then Open that up with a HEX editor and search for the current KERNEL (CE) number.
Onc eyou have obtained the current CE number you then have to replace that HEX string with the 5.1.195 HEX string by editing the OS.nb.
Done.
P.S: dont ask me for the 5.2.1236 HEX string as I dont know it, my roms are based on a newer kernel than those in custel and LVSW's roms.
Click to expand...
Click to collapse
i am using hexedit and sorry for being litte confused but how do i do all that.
jj i would like to use your rom which works with BB but for some reason my power button stops working and i have to reset all the time and i dont want to bother you.
I used black 2.0 work good with bbc 2.1 and bbc 4.0 that is the best for my.
I'm not use black 3.01 because I have problems with my BT ( parrot ck3100) I am waiting for the new version with new drivers to BT.
Another Rom I liked is XDA 0.20, also work good with BBC, anybody know more ROMS work wiht BBC, I think the new ROMS only work good with BBC is Black 2.0, 3.0,3.01. Thanks.
jasjamming said:
ok this is how to do this.
you need to first extract the kernel from the OS.nb
The kernel is in the XIP section, not IMGFS of the rom.
To obtain the XIP section, use rommaster.exe and dumpromx.exe
once you have obtained coredll.dll (the kernel) then Open that up with a HEX editor and search for the current KERNEL (CE) number.
Onc eyou have obtained the current CE number you then have to replace that HEX string with the 5.1.195 HEX string by editing the OS.nb.
P.S: dont ask me for the 5.2.1236 HEX string as I dont know it, my roms are based on a newer kernel than those in custel and LVSW's roms.
Click to expand...
Click to collapse
And finally the last question "How do I know what to search for, before I can replace it ?" was answered in the original thread I mentioned above, in this post - trace the GetVersionEx function.
i am in hexedit and i can not find the hex please tell me what hex to find so i can change it
aih1977 said:
i am in hexedit and i can not find the hex please tell me what hex to find so i can change it
Click to expand...
Click to collapse
I think you better wait for someone else will do this.
Black 3.5 is coming up within next few days and JJ is searching for the string night and day as we speak. Right JJ ? And then again, even thought lvsw and Sleuth255 refused to disassemble for one reason or another, I see other people on this forum, who have SDK and IDA as wallpaper and speak assembler natively, have added this task to their TODO list.
Besides, HTC shall release an official version veeeery soon.
thanks for everything sorry to bother you guys i thought it was easy to do but i am not to talented in this type of things. so i thank you all who tried to help.
aih1977 said:
thanks for everything sorry to bother you guys i thought it was easy to do but i am not to talented in this type of things. so i thank you all who tried to help.
Click to expand...
Click to collapse
Not a problem. Thanks to you we actually have put together a nice summary ... almost a WIKI page on this subject
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?
As is.
Just press the "!COOK.CMD" file. (or make your changes before)
Old opinion:
>>8M of PP - after long time of testing looks as the optimal size for performance/RAM.<<
New opinion:
12M PP looks bit more responsible to interface.
New packages & drivers.
Tweaked several packages - for less memory use.
Tried to put all possible configs in one OEM/xxxconfig folder.
UC ready, - look to _ADDS/Internal Storage forder for example.
Mark all content of "Install" forder as "read only". Or you loose it after install or hard reset.
The best way - look inside "provision.zip" and make your own config file. Put it in "Install" folder and line as
"XML: \Storage\Install\provider.xml" to "sdconfig.txt".
Password for provision.zip you can find at the help page of Connection setup.
You need unsigned HardSPL!
Don't forget about hard reset after first install & make content of "Internal Storage/Install" READ ONLY!
RESOURCES
"LEGO": http://rapidshare.com/users/JW7QII
Snapshots: http://rapidshare.com/users/7L0TM7
Cabs: http://rapidshare.com/users/E8A83X
-=NEWS=----------------------------------
[2009.01.05]
MSXIP21109 & SYS21109(XIP inside) added to "Lego" repository.
-=NEWS=----------------------------------
------Check the time of upload, new version could be there: not the all changes going to the "NEWS" category -------
P.S. Remark for all:
I open this thread for people, who want to make own rom, but don't want spent the time for brutal operations.
Not all components is "mondi's original", - big thanks for
bepe,
swtos,
Niki,
Vic5870,
AVLev,
Prewien,
lexxirae,
and others for ideas and work.
It's only "timepoints" of my kitchen. With bugs, mistakes etc.
Will be glad to see opinions, founded bugs, new ideas.
EVERYBODY CAN USE IT AT ALL, if they use it for private ROM or follow the same "open" politics.
i get errors when extracting. winzip says its corrupt and win rar says invalid or corrupt authenticity information. win rar will complete the extration, but i'm not about to flash anything when there are errors. maybe upload again?
MD5:
18ebc1fbaaca73df8ff6124ad4296db3 *1.97.20755_Diamond.rar
19befa01daf491d6c838fa8d38d8096a *KITCHEN_20755_WWE.RAR
2bdceea4e5642f9f4066ed858041c086 *1.97.20755.nbh
Check it.
I'm downloading back now. Will see.
Used winrar 3.80
..............
1.97.20755_Diamond.rar has checked: passed
1.97.20755.nbh has checked: passed
KITCHEN_20755_WWE.RAR has checked: passed
Thanks man,
going to try it now
If I can do anything, just let me know...
hi,
at first, i have the same problem with extracting (3.8) and authentification,
but it extracts ... i dont know, if some files wouldnt extract?
the second is
"AAAAAAAAAAAAAAAAAAAAAAARGH" !
where you are the last weeks during i flashing my rom with kaiserkitchen
(it's very good, but for beginners its very strong ... with a liitle time spend
and reading here and reading there its gone) ?
i cooked my own rom ... i think its 3 houers before ...
its always the same - iam finishing with this one - than an other cooker/flasher puts a new thread and all the works begin at zero.
but that is it what we love i think.
i will use my rom for 3 or 4 houers than i will test/use your kitchen
thank you for your work.
okokur
p.s.
my english is not so good and the time its gone to morning,
my comment to your thread means positiv/happy. it dont means any angries
Hello!
I repeat: it's not "my" kitchen.
"My" is only changes in OEM/SYS/ROM folders.
I like this kind of kitchen for useful "stepping".
Forgot, where did I find it. Somewhere here
Bit later will be update to 20757 (HD ported).
This kitchen seems of no use to me.
It needs .nb, .wrn and other files which are'n present.
Maybe some explanating how to get them, I would like to try it.
pietrucci said:
This kitchen seems of no use to me.
It needs .nb, .wrn and other files which are'n present.
Maybe some explanating how to get them, I would like to try it.
Click to expand...
Click to collapse
???
Just press !COOK.CMD.
May be damaged archive? Check the md5 sum to arh.
Ok, sorry it's working now...
Another question: a lot of files are from date 10th of July, for example the manila files. Does this mean these files really are so old???
The latest versions of manila are of a newer date are they?
pietrucci said:
Ok, sorry it's working now...
Another question: a lot of files are from date 10th of July, for example the manila files. Does this mean these files really are so old???
The latest versions of manila are of a newer date are they?
Click to expand...
Click to collapse
Marked "stable" original Diamond manila.
If you want the alternative - look to the "_OUT" folder.
Updated to Blackstone's XIP/SYS 20757.
Manila updated to last "official": 1.1.35097.1_1630.38
Style to gray.
I just got my Diamond 2 weeks ago. I cook my first ROM using your kitchen tree but I have some questions:
1. Why the setting up screen is all black ? I thought there were some sort of Windows Mobile 6 background
2. I tried to set up bluetooth but it shows me a message box with something like "No bluetooth hardware"
I follow the instructions by just clicking !Cook.cmd. I didn't change anything in your packages. Did I do something wrong ?
Please advice. By the way, thanks for this kitchen tree.
dafeke said:
1. Why the setting up screen is all black ? I thought there were some sort of Windows Mobile 6 background
Click to expand...
Click to collapse
It's just my choice: less using rom/ram memory. And not important at all. You can use yours pictures. It is the kitchen, isn't it?
dafeke said:
2. I tried to set up bluetooth but it shows me a message box with something like "No bluetooth hardware"
I follow the instructions by just clicking !Cook.cmd. I didn't change anything in your packages. Did I do something wrong ?
Click to expand...
Click to collapse
I'll see. I use BT very seldom. Didn't check it, just put the packages.
mondilv said:
It's just my choice: less using rom/ram memory. And not important at all. You can use yours pictures. It is the kitchen, isn't it?
I'll see. I use BT very seldom. Didn't check it, just put the packages.
Click to expand...
Click to collapse
I coocked my ROM with version 20755: everything's fine here with bluetooth (and all other stuff). I use bluetooth for my carkit, works fine.
I benchmarked this ROM with my usual benchmarks: it's pretty fast compared to others! I left out Opera and Google Maps, but I don't think that makes a big difference in benchmark results.
I will try your Blackstone upgrade this evening, I'm curious if that's faster than the 20755... (in fact I don;t think so).
There is one strange thing in this one: I can't change pagepool. Using pagepoolchanger.exe it says it can't find the right address...
Keep you informed...
Thank you mondilv for the this kitchens! Great job
pietrucci said:
I coocked my ROM with version 20755: everything's fine here with bluetooth (and all other stuff). I use bluetooth for my carkit, works fine.
I benchmarked this ROM with my usual benchmarks: it's pretty fast compared to others! I left out Opera and Google Maps, but I don't think that makes a big difference in benchmark results.
I will try your Blackstone upgrade this evening, I'm curious if that's faster than the 20755... (in fact I don;t think so).
Click to expand...
Click to collapse
Agree. I did benchmarks too. (?)
BT fix - in the first post (from 20755 SYS). Works now.
pietrucci said:
There is one strange thing in this one: I can't change pagepool. Using pagepoolchanger.exe it says it can't find the right address....
Click to expand...
Click to collapse
pagepoolchanger.exe don't works to Diamond (use search - don't remember, where is the info). Use hex editor.
...and NB container is reduced by uldr, - only one needed address.
pietrucci said:
Keep you informed...
Click to expand...
Click to collapse
Thanks for cooperation!
mondilv said:
Agree. I did benchmarks too. (?)
Click to expand...
Click to collapse
I suppose you use the ? because you don't know why I make this remark? Well, if you like take a look at my thread: http://forum.xda-developers.com/showthread.php?t=406640, you can compare this ROM with many others, all tested on the same device, under the same circumstances, more or less.. I will add this ROM's benchmark results later this evening.
mondilv said:
pagepoolchanger.exe don't works to Diamond (use search - don't remember, where is the info). Use hex editor.
...and NB container is reduced by uldr, - only one needed address.
Click to expand...
Click to collapse
PagePoolChanger DOES work on most 'normal' Diamond ROMs, I've used it many times before. But I guess it conflicts with the uldr thing... no problem.
here friend... like mentioned in a PM sent you this morning... I'm porting some pieces of your base sys/xip for including in my rom (dia duit), of course I'll mention that the base rom comes from your hard work
instead of upgrading the whole sys I prefer to choose faster/smaller dlls between different sys
anyway also my rom is open, because I strongly believe that this is the only way to proceed to a faster development... by sharing infos each other
but I'll prefer to share the whole kitchen on my 1st stable release, now we are at v08, because till now my rom has some bugs
thx mate!
bye,
davide
pietrucci said:
I suppose you use the ? because you don't know why I make this remark? Well, if you like take a look at my thread: http://forum.xda-developers.com/showthread.php?t=406640, you can compare this ROM with many others, all tested on the same device, under the same circumstances, more or less.. I will add this ROM's benchmark results later this evening.
PagePoolChanger DOES work on most 'normal' Diamond ROMs, I've used it many times before. But I guess it conflicts with the uldr thing... no problem.
Click to expand...
Click to collapse
here how to change PP on diamonds:
open final .nbh file with a hex editor (I use pspad)
search the following hex value: 389FE550089FE5
as you find it change next two numbers (in an original rom, these two values are 00 25)
search again for the same hex value, again you need to modify the adjacent two values (in case of an original rom, these two values are 03 25)
values:
for pp 0 Mb: 00 25
for pp 8 Mb: 02 25
for pp 12 Mb: 0C 26
for pp 16 Mb: 10 26
of course I wasn't able to find alone... I found thx to the great & nice Seatone
have fun
pietrucci said:
I suppose you use the ? because you don't know why I make this remark?
Click to expand...
Click to collapse
I was bad surprised too. Quite big diff between close versions. About 5%, isn't it?
After trying several combination of xip/sys me like 20755 at last time.
Or xip757/sys755 - no bad too.
pietrucci said:
Well, if you like take a look at my thread: http://forum.xda-developers.com/showthread.php?t=406640, you can compare this ROM with many others, all tested on the same device, under the same circumstances, more or less..
Click to expand...
Click to collapse
I good know your thread
pietrucci said:
I will add this ROM's benchmark results later this evening.
Click to expand...
Click to collapse
Early, I think. Can't to call its rom stable. Just found more bugs, think not the last for today (lighting for missed call is absent; green element in manila)
I return to home now, so new version could be tonight.
pietrucci said:
PagePoolChanger DOES work on most 'normal' Diamond ROMs, I've used it many times before. But I guess it conflicts with the uldr thing... no problem.
Click to expand...
Click to collapse
May we use different versions?
"My" looks properly worked, but by devhelth.exe - PP didn't changed.
When I try to build a rom with the ervius kitchen, I become this error:
Ideas?
A week ago there was no problem
x-sergo said:
When I try to build a rom with the ervius kitchen, I become this error:
Ideas?
A week ago there was no problem
Click to expand...
Click to collapse
Can you share your build log (Build_log.txt)? This is usually seen when there are far too many duplicate modules (overwrites), but it could be something else.
what should I do with the overwriting?
p.s. i deleted some part of log, so I can upload the file
x-sergo said:
what should I do with the overwriting?
p.s. i deleted some part of log, so I can upload the file
Click to expand...
Click to collapse
can you zip and upload the whole log?
here we go :=)
x-sergo said:
here we go :=)
Click to expand...
Click to collapse
1/ the first 4 warnings should be avoided (After MSXIPKernel is loaded)
Not really seen this happening elsewhere
2/ try cooking without manila and see if you can proceed minus the error
This may just work for you. If it does, next time around, cook again with another manila/sense version just to make sure that something in manila isn't causing the conflict with the other base files.
3/ another way to troubleshoot is to try with some other XIP/SYS if available.
This will rule out issues with the build files
This error comes when there are too many overwrites. Try and avoid the overwrites to a bare minimum.
PS: I've used GenY manila with his kitchen and it works super fine. It's just a case of conflicting overwriting that isn't going well with the kitchen.
10x for the answer, but the kitchen was working 2 weeks ago! i havent change anything...
for my kitchen I used the gen.y kitchen too. i was made a zip file from the whole working kitchen from 20. Dec. Deleting all the files and unzipping the kitchen to a new folder was without result too
anyway thanks for the help
I have the same error and can't figure out what's wrong. If you ever figured this out, please post your solution.
Thanks.
FlopShot
Try to remove "read only" attribute for all files in your kitchen.
Right click on Kitchen folder (or whatever you name it), Choose Properties, Uncheck Read Only attribute then click on OK
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