Related
Hiya everyone,
I'm a bit of a noobie when it comes to flashing phones - but I'm really wanting to get a stable reliable version of WM6 on my Tytn. I've had the HTC Offical WM6 ROM (that keeps hangin when the phone goes to sleep - have to SR to get the phone working again), I've tried Black Satin (the WiFi/new Com Manager doesn't seem to work very well).
There seems to be tonnes of different ROMs - and I'm wondering is there one that stands out above the rest for reliability?
I've done a search and not found the answer to this - so anyone with any info....?
Ta people
A
My best recommendation is READ the threads on the different roms.
The comments on them will give you a good idea of how the ROMs are running on people's phones.
The Best Rom Ever:
Schap's 3.57a, or any ROM proudly made by Schap's.
thenoble06 said:
Hiya everyone,
Click to expand...
Click to collapse
Seems like a daily occurrance around here......I say LVSW 5-7 or VP3G Ver 2.0 Hyrid or VP3G Ver 3.0 or Schaps or Dopod Official or Att official or Black or CUSTEL....... (Sorry I missed a some cooks names)
GldRush98 said:
My best recommendation is READ the threads on the different roms.
Click to expand...
Click to collapse
Fair enough point I rekon - its just there are so many ROMS - and soooo many thread replies for each ROM - i could be here years reading
cabi.costa said:
The Best Rom Ever:
Schap's 3.57a, or any ROM proudly made by Schap's.
Click to expand...
Click to collapse
I'd have to agree with this except for one minor thing.....BB Connect will not work with Schap's Rom.
Anyone willing to Hex Edit it and make it work? I PM'd Schap however I'm assuming he's already flooded with requests.
I guess we can help by suggesting things you may want to look out for:
Only some of these may/may not be important to you...
BBConnect compaitibility
Big Storage, Free RAM & Storage
Smart Dialling
3G Video Dialling
Office Version (They're all pretty much 2007 now, but not all have OneNote)
BT issues - Stereo, DUN vs/and Internet Sharing
Included apps, Standard File Explorer
Included Dialpad style & functions, Kaiser/std ?
Included CommManager & Style
Speed & Stability
MMS/SMS combins (Arcsoft Version)
Included operator settings?
Included Homescreens - HTC Weather etc etc
VOIP functionality
PTT functionality
I'm sure there are loads more...
Lets turn this thread into something useful. Rather than this rom is better than that, etc, lets help the Noobs by adding to this list of things they may want to consider.
my £0.02.
i've tried most, and i'd definitely go for schap's, preferably 3.57
Khristopher said:
I'd have to agree with this except for one minor thing.....BB Connect will not work with Schap's Rom.
Anyone willing to Hex Edit it and make it work? I PM'd Schap however I'm assuming he's already flooded with requests.
Click to expand...
Click to collapse
All current ROMs ( and you do want to run the latest, as 99% ROMs released before June have issues ) on this forum are based on the same release. So technically speaking they are all same. The difference is added / removed applications and how well this was done.
Regarding BBC - even if the ROM does not state the compatibility - it is a matter of 4 simple steps to make it compatible. 1) Download the ROM file, unrar it to desktop - you'll get 2 files extracted .exe and .nbh ( RUUWrapper.exe RUU_signed.nbh ) 2) Run winhex ( http://www.x-ways.net/ ) and load the .nbh file, HEX search for the first string in my signature and replace it with the second string. There is going to be 2 occurences you'll have to replace. Save the .nbh file 3) execute the .exe file to flash the .nbh ROM file to your device 4) after the flash use a registry editor to change [HKEY_LOCAL_MACHINE\System\Versions] "Aku"=".2.3.0"
Of course you have to be careful and all disclaimers apply
If this is over your head - just PM me.
moisha said:
All current ROMs ( and you do want to run the latest, as 99% ROMs released before June have issues ) on this forum are based on the same release. So technically speaking they are all same. The difference is added / removed applications and how well this was done.
Regarding BBC - even if the ROM does not state the compatibility - it is a matter of 4 simple steps to make it compatible. 1) Download the ROM file, unrar it to desktop - you'll get 2 files extracted .exe and .nbh ( RUUWrapper.exe RUU_signed.nbh ) 2) Run winhex ( http://www.x-ways.net/ ) and load the .nbh file, HEX search for the first string in my signature and replace it with the second string. There is going to be 2 occurences you'll have to replace. Save the .nbh file 3) execute the .exe file to flash the .nbh ROM file to your device 4) after the flash use a registry editor to change [HKEY_LOCAL_MACHINE\System\Versions] "Aku"=".2.3.0"
Of course you have to be careful and all disclaimers apply
If this is over your head - just PM me.
Click to expand...
Click to collapse
Definitely not over my head......and THANK YOU for putting it in simple steps.
I've read thread upon thread upon thread here trying to figure out how to do this and there is just so much information, it's almost too much and too confusing at times.
I'll post back whether or not I was successful!
Khristopher said:
Definitely not over my head......and THANK YOU for putting it in simple steps.
I've read thread upon thread upon thread here trying to figure out how to do this and there is just so much information, it's almost too much and too confusing at times.
I'll post back whether or not I was successful!
Click to expand...
Click to collapse
Hmmm......doesn't seem to work. It looked like it connected the first time after booting up and setting up my Rogers info.....but then it wouldn't connect again.
Just start kit. For further cooking.
Based at official release (and stable, I hope,- don't like to be beta-tester for HTC "in the dark").
It's new way for me (just began to use WinMob by Diamond), so don't bite me too much
Don't forget about Hard-SPL!
Few cosmetic changes & a little tweaked. UC ready.
In OEM left TouchFlo only.
In SYS out: OneNote, PowerPoint, WindowsLive, Help & other rubbish.
In "Install" folder - example only. You can change it to your own provider (look to OEM\CONNECTIONSETUPDB - password I found at XDA) or just use ConnectionSetup.
The most tweaks - in OEM\xxxconfig
Be careful to finish.xml - it's important file!
(return to "Internal Storage". Manila start including in this file too. You can customise it up to you. Same as *.rgu in this folder)
To find the bugs&errors better together, I think
Ideas&remarks - welcome!
It's OPEN PROJECT.
Kitchen: http://rapidshare.com/files/143594363/WWE_1.93.479.3_kitchen.zip
Example ROM (with pass for provision.zip):
http://rapidshare.com/files/143600258/1.93.19965.Light.rar
For make the same - just press !COOK.CMD in the kitchen.
Lighted packages:
http://rapidshare.com/files/144298572/PACKAGE_Diamond_PhoneCanvas.RAR
http://rapidshare.com/files/144138802/PACKAGE_Diamond_QuickGPS.RAR
The trick - in change heavy bmp files to compressed/indexed png.
And patched dll/exe, for use another files.
Not sure about using system resources in this way - up to you. Try.
Changes: http://rapidshare.com/files/144298443/changes_to_kitchen.rar
(Corrected ROM container: 19965 now. Was 20273 - just mistake. And help engine)
can I just install your rom on my Diamond?
Would like to try it, but dont want to fool around with the Kichen stuff
Been reading much on cooking the last days. This looks like a good start!
Thanks for sharing. Hope I can create my own Diamond ROM from here. If it's good enough for some of my friends I will share it on XDA as well
teddyen66 said:
can I just install your rom on my Diamond?
Click to expand...
Click to collapse
Not see the reason - only base functions.
You are right, but it's the fastest ROM I've ever tried
But like you said, it's very basic. Camera is not working, so you need to add all these yourself.
Now watching the kitchen files.. .."WinRAR gives the following message: Invalid or corrupt authenticity information"
It does seem to extract just normal. Is the RAR file save?
update: You might even remove the Office part from the light ROM??
mccune said:
Now watching the kitchen files.. .."WinRAR gives the following message: Invalid or corrupt authenticity information"
Click to expand...
Click to collapse
Hm. "Top" level - zip. Inside - rar. Going to try download back. May be corrupted...
No, everything OK to archive.
I use rar v.3.71
mccune said:
You might even remove the Office part from the light ROM??
Click to expand...
Click to collapse
Word & Excel till alive
mccune said:
You are right, but it's the fastest ROM I've ever tried
Now watching the kitchen files.. .."WinRAR gives the following message: Invalid or corrupt authenticity information"
It does seem to extract just normal. Is the RAR file save?
Click to expand...
Click to collapse
Its 7-Zip i think extracts ok
I will give this a try, other kitchens didn't work out for me very well.
Thanks man ...
Help system
I think idea to remove the help system absolutely is not the best.
Sometimes apps need it for normal work. May keep help engine alive?
Any opinions?
Please tell me one usefull hint that's provided to you because of the Help function?
For me it's wasted space on every device I've owned. If I encounter any problem they go beyond the help files
Looks pretty complicated with no real guide, will look into other kitchens!
I talk about engine (hwhelp) only. The most help files - "dead cargo", of course.
After try to push "help" button at some apps - error, could make system unstable.
P.S. made two "light" packages. ( see in the first post).
It use a little less memory, I hope.
Congratulations for this new project! If you need any help about a multilanguage (Italian) version... I'm ready!
sev7en said:
Congratulations for this new project! If you need any help about a multilanguage (Italian) version... I'm ready!
Click to expand...
Click to collapse
Thanks for support
I think, change the locale - it's only change the *.mui & may be other files in folders *_0409. Change to Italian locale - _0***, don't know exactly.
Could you try it?
Found the mistake - "alien" rom container (from 20273) in the kitchen.
Just accident.
May be it's nothing, but...
- in the first post + hwhelp.exe: changes_to_kitchen.rar
Tricks
Stop unused services (functional don't loose) - will start on demand:
[HKEY_LOCAL_MACHINE\Services\BTAGSVC]
"Flags"=dword:00000004
[HKEY_LOCAL_MACHINE\Services\BthAsPlugin]
"Flags"=dword:00000004
[HKEY_LOCAL_MACHINE\Services\BTHIDSVC]
"Flags"=dword:00000004
[HKEY_LOCAL_MACHINE\Services\OBEX]
"Flags"=dword:00000004
[HKEY_LOCAL_MACHINE\Services\QuickGPS]
"Flags"=dword:00000004
[HKEY_LOCAL_MACHINE\Services\WirelessService]
"Flags"=dword:00000004
It's THE SAMPLE. (but I use it)
May stop any more? Biotouch, for example?
------------------------------------------------------------------------
Start HTCVolumeControl.dll without taskmanager, or if you use another TM:
[-HKEY_CURRENT_USER\Software\HTC\BootLauncher\Services\HTCVOLUME]
[HKEY_LOCAL_MACHINE\Services\HTCVOLUME]
"Dll"="HTCVolumeControl.dll"
"Order"=dword:0000000c
"Index"=dword:00000000
"Info"=dword:00000000
"Prefix"="VOL"
Tested on Raphael VolumeControl
------------------------------------------------------------------------
Somebody can explain how to (EXACTLY! step by step) change OS, XIP, SYS in this kitchen? I've read a lot of tutorial but I didn't understand how...
In example, I've got:
1) this kitchen and this "base" rom
2) another diamond rom with 20748 xip build.
If I would to update OS, XIP and SYS to newer, what I have to do?!
GriFolle said:
Somebody can explain how to (EXACTLY! step by step) change OS, XIP, SYS in this kitchen? I've read a lot of tutorial but I didn't understand how...
In example, I've got:
1) this kitchen and this "base" rom
Click to expand...
Click to collapse
You don't neet "base" rom (or what you mean?) it's example only.
If you talk about rom\os.nb in the kitchen - it's just container for rom, which is empty.
GriFolle said:
2) another diamond rom with 20748 xip build.
If I would to update OS, XIP and SYS to newer, what I have to do?!
Click to expand...
Click to collapse
Just delete oem, rom, sys & make you own "tree"
Thanks for your very QUICK reply Modilv!
So, I have just to take the parts of (maybe more) diamond romS that I need (including OS.nb??) and put theme in your kitchen..?
So simple?!
PS: no "porting" xip or something like that?
TIA
It't not "my" kitchen (just add bepe's utility to final step)
I made the "tree" only.
You can do the same.
Hello
I'm cooking my own rom and I've one small irritating problem. I've set rom version as: 1.0. In device information it shows properly, but when my pda is starting, on first splash screen it shows me that rom version is: 3.0. I know it is somewhere in nk.exe but I've problem to locate it...
Best regards
tomme45i
tomme45i said:
Hello
I'm cooking my own rom and I've one small irritating problem. I've set rom version as: 1.0. In device information it shows properly, but when my pda is starting, on first splash screen it shows me that rom version is: 3.0. I know it is somewhere in nk.exe but I've problem to locate it...
Best regards
tomme45i
Click to expand...
Click to collapse
You can do that from the kitchen. I know ervius kitchen has two dialog boxes on the left, sort of middle of the screen, where you can set ROM date and version. It will patch the nk.exe accordingly.
Watch it though: if you use the patched nk.exe for bluetooth sound fix, you will not be able to set the whole version to your liking, there will be some 1 digit fixed value that cannot be changed - if I recall well.
P.S.: Sorry tomme, don't really read the Trinity threads anymore. But I will take a look every now and then, promise!
Yes I know PkgToolsBuildos, but this program always set rom version 3. when I edit S000 from nk.exe by hand, it is still show me rom version 3.x but then I have proper rom version in device information.
tomme45i said:
Yes I know PkgToolsBuildos, but this program always set rom version 3. when I edit S000 from nk.exe by hand, it is still show me rom version 3.x but then I have proper rom version in device information.
Click to expand...
Click to collapse
That's because of the nk.exe that has already been patched. Try another nk.exe or an older buildOS.
tnyynt said:
Try another nk.exe or an older buildOS.
Click to expand...
Click to collapse
I try on PkgToolsBuildos 4.2b3 and on 4.3b1. In BuildOS->Rom ver. in Boot there is number 3 even before I load rom. Where can I find older PkgToolsBuildos cause I'he tryied another nk.exe without luck.
tomme45i said:
I try on PkgToolsBuildos 4.3b1 and on 4.3b3. In BuildOS->Rom ver. in Boot there is number 3 even before I load rom. Where can I find older PkgToolsBuildos cause I'he tryied another nk.exe without luck.
Click to expand...
Click to collapse
Try with this one.
tnyynt said:
Watch it though: if you use the patched nk.exe for bluetooth sound fix, you will not be able to set the whole version to your liking, there will be some 1 digit fixed value that cannot be changed - if I recall well.
Click to expand...
Click to collapse
it can be changed, it's just a hardcoded MOV instruction in assembly
tnyynt said:
Try with this one.
Click to expand...
Click to collapse
tnyynt thank you for you answer, but even on older version situation is the same. Program always overwrite 1st digit. Here is screenshot from older version buildos+package_tools-4.1b1:
You can't change the first digit in ROM version, no matter which nk.exe you try to change.
On the old nk.exe (the one used to fix the losing password bug for some users) you'll always have 0. before whatever you want your ROM version to be.
On the newer nk.exe you'll always have 3. before whatever you want your ROM version to be.
That's something you just can't change, because it's an hardcoded value and this was the reason why my ROMs for trinity were 3.something (because when I started cooking I was using the newer nk.exe) and even after changing to the old nk.exe (to solve the losing password bug for some users - a problem I never had in my device), I had to start numbering my ROM as 0.3.something.
My advice:
If you don't have the password bug with your device, and are not planning on releasing the ROM, use the newer nk.exe and number your ROM 3.1.0, and forget about the 3..
The ROM version in Device Info is a completely different thing. That value is not hardcoded anywhere, and since it's a registry value, you can put whatever you wish and it will display properly.
In conclusion, if you're using the PkgToolsBuildos (doesn't really matter which version you're using) to change the ROM version (and this is responsible only for the value that appears on the boot screen), leave the left field as it is, and change only the right field to what you want and save changes.
I hope this will clear your doubts about this. Happy cooking!!
I don't know the difference between this two version of NK.exe so FInixNOver thank you for explanation!
I release my roms on polish forum. First nine was based on old NK.exe, so the last was 0.9. Now when I try new NK.exe I was surprised that my rom version in boot is starting from 3.
BTW. I think only first digit is hardcoded, cause I can change dot symbol by hex editing S000 file.
One more time FInixNOver thank you for your reply!
FInixNOver said:
That's something you just can't change, because it's an hardcoded value
Click to expand...
Click to collapse
huh? it is an not one time writable value. you can change it with a simple assembly patch that I referred to above
cmonex said:
huh? it is an not one time writable value. you can change it with a simple assembly patch that I referred to above
Click to expand...
Click to collapse
I stand corrected. I just said that because I was never able to change that value. So if you say it's possible, even better!!
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!!!
Well ... I have repaired my Hermes yesterday and now I'm trying ROMs here and none of them really suits me.
So your SJK came in the right time. I did few ROMs for myself last year, so I'm gonna try your SJK probably this evening.
And if it will work flawlessy, I'm considering donation.
Impressive..
Downloading and will hopefully be trying this out soon.
Let me know if you run into any problems with the native nk and changing the pagepool. (I don't have a test device, unfortunately.)
ivanmmj said:
Let me know if you run into any problems with the native nk and changing the pagepool. (I don't have a test device, unfortunately.)
Click to expand...
Click to collapse
I am cooking a 23529 native build now and will know here soon
Well, I have built 6.5.x ROM with native kernel and 16MB pagepool. I didn't add anything in the ROM and I'm missing Camera, CommManager, ClearStorage and stuff like this in the ROM. Suppose I have to add them externally.
Now I'm gonna try adding some things and changing pagepool etc.
pajousek said:
Well, I have built 6.5.x ROM with native kernel and 16MB pagepool. I didn't add anything in the ROM and I'm missing Camera, CommManager, ClearStorage and stuff like this in the ROM. Suppose I have to add them externally.
Now I'm gonna try adding some things and changing pagepool etc.
Click to expand...
Click to collapse
You have to actually add them in the EXT packages. They are not built in so that you can choose your own. I stripped the OEM and created packages of all required programs and made them into EXT packages.
Ooops, my bad. I've just extracted EXT, SYS, SJK, HERMES archives and didn't check the wrong paths. Because everything puts itself in Sources and the EXT has got Working_Folder/EXT instead of Sources/EXT.
I was wondering why I can't see any EXT things in the osKichten.exe
I must be doing something wrong then cause mine won't go past the boot screen using native. I used everything default. Will try again.
This has happened to me the first time i tried this Kitchen ... then I've tried it again and it worked.
But I'm havning problem with the EXT. I can't select packages from the folders. I can just select folders. :\
EDIT: Ok, I surreder - where are the C_cingular, C_xyz.cab things? I can't find them anywhere to get rid of them.
pajousek said:
Ooops, my bad. I've just extracted EXT, SYS, SJK, HERMES archives and didn't check the wrong paths. Because everything puts itself in Sources and the EXT has got Working_Folder/EXT instead of Sources/EXT.
I was wondering why I can't see any EXT things in the osKichten.exe
Click to expand...
Click to collapse
You have have accidently downloaded v0.7 of the EXT which is a COMPLETELY different kitchen.
This has happened to me the first time i tried this Kitchen ... then I've tried it again and it worked.
But I'm havning problem with the EXT. I can't select packages from the folders. I can just select folders. :\
EDIT: Ok, I surreder - where are the C_cingular, C_xyz.cab things? I can't find them anywhere to get rid of them.
Click to expand...
Click to collapse
I'm not sure what you mean. Can you please post a screenshot?
ivanmmj said:
You have have accidently downloaded v0.7 of the EXT which is a COMPLETELY different kitchen.
I'm not sure what you mean. Can you please post a screenshot?
Click to expand...
Click to collapse
Well, the first issue (not showing apps) was cause by the 0.7 version instead of 0.8 ... i really should give more attention to what I'm downloading.
The EDIT line, about C_Cingular_GoodEmail*.cab, PT_Cingular_Whitelist* etc. - those are apps which are automatically installed after first boot. I suppose it's cause by the line "EXEC:\Extended_ROM\autorun.exe" in PreConfig.txt in OEMOPERATORS. But - where does that autorun.exe has it's config? and where's Extended_ROM in the Kitchen? Because afaik it isn't the same as EXT?
EDIT: I got an idea - aren't those cabs just remains of the ExtROM from AT&T ROM? Then, howto delete them? By making my ROM BigStorage? :|
pajousek said:
Well, the first issue (not showing apps) was cause by the 0.7 version instead of 0.8 ... i really should give more attention to what I'm downloading.
The EDIT line, about C_Cingular_GoodEmail*.cab, PT_Cingular_Whitelist* etc. - those are apps which are automatically installed after first boot. I suppose it's cause by the line "EXEC:\Extended_ROM\autorun.exe" in PreConfig.txt in OEMOPERATORS. But - where does that autorun.exe has it's config? and where's Extended_ROM in the Kitchen? Because afaik it isn't the same as EXT?
EDIT: I got an idea - aren't those cabs just remains of the ExtROM from AT&T ROM? Then, howto delete them? By making my ROM BigStorage? :|
Click to expand...
Click to collapse
Fixed for next build. ^_^
For now, just remove the preconfig.txt file.
Please report any future bugs to the bug tracker. (There are way too many threads to keep track of all of them.)
I've registered to bugtracker ... and the confirmation email didn't come, so I can't post new bugs. I guess I have to post it as guest?
pajousek said:
I've registered to bugtracker ... and the confirmation email didn't come, so I can't post new bugs. I guess I have to post it as guest?
Click to expand...
Click to collapse
I activated you manually. I'm not sure why it's not sending out the emails. I'll look at the code of the site.
I take it this isn't bigstorage? If not do you plan to have one bigstorage? I'd like to be able to do bigstorage in 6.1 and 6.5 and this looks like my best option..
thanks
Since the bugtracker is broken:
These things are buggy:
any Connection Wizard - I can't get it to work
Dialer - Every dialer is buggy and if I try to cook there else OEM Dialer (found by google), it doesn't work too
ClearStorage - doesn't do hardreset
Then I'd appreciate battery.dll which is by 1% and not 10%.
Making the ROM BigStorage would be a big plus too. And AFAIK I shouldn't have 39MB RAM with 6MB PagePool? 39MB is for 16MB PP, right?
MrDSL, are you experiencing anything of these issues too?
pajousek said:
Since the bugtracker is broken:
These things are buggy:
any Connection Wizard - I can't get it to work
Dialer - Every dialer is buggy and if I try to cook there else OEM Dialer (found by google), it doesn't work too
ClearStorage - doesn't do hardreset
Then I'd appreciate battery.dll which is by 1% and not 10%.
Making the ROM BigStorage would be a big plus too. And AFAIK I shouldn't have 39MB RAM with 6MB PagePool? 39MB is for 16MB PP, right?
MrDSL, are you experiencing anything of these issues too?
Click to expand...
Click to collapse
Strange. I'll have to test the connection wizards on the wing.
The dialers work fine on the wing. Does the dialer named Hermes work? (It's directly from the Hermes.)
ClearStorage - Your device might require an older clearstorage. I'll have to look for one.
That sounds like the native 6.5 nk isn't getting its pagepool changed.
I'll see about that. The Hermes 6.5 nk is notorious for most pagepool tools not working on it.
As far as the bigstorage. Give me a link to it and I will see about including it.
well, i'll try the not-native kernel (what disadvantages it has anyways?)
about bigstorage & clearstorage & dialer - i'll do some searching and testing and send you working links (since you don't have testing device).
ivanmmj said:
Strange. I'll have to test the connection wizards on the wing.
The dialers work fine on the wing. Does the dialer named Hermes work? (It's directly from the Hermes.)
ClearStorage - Your device might require an older clearstorage. I'll have to look for one.
That sounds like the native 6.5 nk isn't getting its pagepool changed.
I'll see about that. The Hermes 6.5 nk is notorious for most pagepool tools not working on it.
As far as the bigstorage. Give me a link to it and I will see about including it.
Click to expand...
Click to collapse
I have yet to get a ROM past the boot screen So I dunno..
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