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.
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.
Here's a new ROM for the Excalibur cooked on the new 20282 core and the system partition from the newest HTC smartphone, the S740 "Rose".
This is a WWE (world wide English) only ROM.
Applications included in this ROM are:
- HTC Album
- Tegic T9 with English available
- TMobile Dash keyboard layout file by default
- Adobe Reader LE
- HTC Audio Manager
- Automatic GPRS settings application
- Windows Live
- Windows Live Messenger
- HTC Streaming Media
- Office Mobile
- HTC Weather
- The new HTC dialer application
- HTC CommManager
- This ROM is "UC" (user customization) capable!
- Chome Configurator
- So much more...
This ROM includes the new sliding panels from HTC, which open up a world of opportunities for customization.
INSTRUCTIONS for flashing:
1. Run the downloaded exe. It should automatically unpack and present a black command prompt window.
2. Make sure you remove your storage card from the phone before the next steps.
3 .Follow the instructions in the black window. Do NOT reboot when the SDA unlocker tells you to reboot the phone. It's not necessary.
4. You might get a prompt asking you if you want to run the spl program. Just say yes. At that point you should get a white screen.
5. If for any reason you're not seeing a white screen, you did something wrong and you need to try again.
6. Flash the ROM following the instructions in the flashing utility.
You can expect the phone to be "stuck" on the HTC logo for about 2 1/2 minutes the first time. After that, it should only take about 40-45 seconds for the phone to reboot.
INSTRUCTIONS for recovery in case something goes wrong:
Turn your phone completely off. Pushing the camera button in, plug in your usb cable. The tricolor, bootloader screen will come up and you can flash your regular OEM ROM which can be downloaded from one of the stickies.
I recommend flashing the modified bootloader made by jockeyw2001. It's attached to this post.
What it does is, it CID unlocks your phone, so you don't have to use the softSPL everytime you want to flash a ROM. It also makes recovery from a bad flash much easier, where you dont have to hunt for your original manufacturer's ROM to load in order to resurect the phone.[/CENTER]
Download links
FULL Version:
http://www.sendspace.com/file/1j0dsu
Rapidshare: http://rapidshare.com/files/171877492/Excalibur_NRG_Rose_v1.4.1_.exe
============================================================
SuperLite version 1.4.1
Stuff removed:
HTC Ringtones
Bluetooth FTP/SAP/OBEX
Bluetooth HID Drivers
MS Office
ONeNote
Chome COnfigurator
Streaming Media Player
Rinku's Top Bar
UC Autoconfig
AdobePDF
AudioManager
Cyberon VoiceTag
HTC Album
Lockstream DRM
Picture Enhancement plugin
QuickNotes
VoiceRecorder
Inbox Menu Extender
PHM Registry Editor
Windows Live
WM5 Storage
BaseHue Expres
Welcome Center
Connection Setup
Sendspace: http://www.sendspace.com/file/8ws4ab
Rapidshare: http://rapidshare.com/files/172168545/Excalibur_NRG_Rose_v1.4.1_LITE_.exe
Here's a link to donate via PayPal.
PayPal Donate Link
time to test it out :O
Cool...
I'll wait for teh superlite before I test it though.
many thanks for this...
Appreciate it.
If you guys/gals find any bugs, NOW is the time to report them, before I release the next version... Thanks.
Nice rom, it seems really fast man. Thanks for this once again.
USA t9 on ROM seem to have problems? here's the solution:
http://forum.xda-developers.com/showpost.php?p=2074399&postcount=1148
Oh mine did not have any problems with t9...
Thanks for putting this out! The ROM does seem a bit quicker and I'm not seeing any bugs.
Wow, I'm still running Rick's Kavana Remake V18... I've been waiting until most of the bugs have been worked out, but now that you mention a superlite version tempts me even more. Keep up the good work man!
johnambler41577 said:
Wow, I'm still running Rick's Kavana Remake V18... I've been waiting until most of the bugs have been worked out, but now that you mention a superlite version tempts me even more. Keep up the good work man!
Click to expand...
Click to collapse
Maaan.. you're still in the dark ages. lol j/k It it still works for you, why change ? heh I wouldn't. Unless of course, you have the flashing bug.. haha
blackshin0bi said:
USA t9 on ROM seem to have problems? here's the solution:
http://forum.xda-developers.com/showpost.php?p=2074399&postcount=1148
Click to expand...
Click to collapse
Hmm interesting. I installed that cab over 1.4 and the tab key DID behave like it's supposed to. I will make sure to integrate this fix in the next release (including the lite release).
I went to find the t9 file mainly because there was no predictive text showing up for me after I flashed this ROM twice. No matter the cause, this seemed to fix it up. One other thing though, the ROM doesn't seem to make any changes when I add the cpr entry to make it show the day of the week, is there something I'm doing wrong?
Last 'problem' is whenever I choose Chome slim, I never have gotten a slim programs list like I see in your screens. Does my phone hate me?
Thanks for your work by the way
blackshin0bi said:
I went to find the t9 file mainly because there was no predictive text showing up for me after I flashed this ROM twice. No matter the cause, this seemed to fix it up. One other thing though, the ROM doesn't seem to make any changes when I add the cpr entry to make it show the day of the week, is there something I'm doing wrong?
Last 'problem' is whenever I choose Chome slim, I never have gotten a slim programs list like I see in your screens. Does my phone hate me?
Thanks for your work by the way
Click to expand...
Click to collapse
Hmmm I never use predictive text, so I guess I never noticed that anomaly. The cab should fix it though...
These new ROMs have a different system for editing CPR files. The CPR file is actually declared in the home.xml file found in application data/home. You have to edit one of those files, declare a custom cpr file and then go drop that file in the \windows directory. OR, you could just edit the HTC cpr file that are already in the windows directory.
Again, with the slim panels, you have to make sure the OS knows about them. THe easiest way is to rename the slim CPRs to the HTC cprs and just overwrite the htc cprs in \windows.
is there any way to set the directory in HTC Audio Manager?
Superlite?! Inquiring minds want to know.
blackshin0bi said:
is there any way to set the directory in HTC Audio Manager?
Click to expand...
Click to collapse
No idea... don't use it. I would assume it searches for all your stuff on the storage card. I dont know...
The Rotagilla said:
Superlite?! Inquiring minds want to know.
Click to expand...
Click to collapse
Well you know.. there's lite ROMs out there with just the basic apps included. I will make a light version as well as a SUPER light version with everything stripped. That way, people can just add what they need or want and that's it
NRGZ28 said:
Well you know.. there's lite ROMs out there with just the basic apps included. I will make a light version as well as a SUPER light version with everything stripped. That way, people can just add what they need or want and that's it
Click to expand...
Click to collapse
Very cool, downloading 1.4 right now. Sent you a PM as well about a separate matter.
Superlite?
When is it coming?
I have been working on this new ROM Kitchen project over the last months.
Public beta can be found here:
http://www.darkforcesteam.com/showthread.php?p=3560
Downloading this minute. Is it also for old devices? (Blue Angel?)
Sounds great, thanks for this kitchen
motisu said:
Downloading this minute. Is it also for old devices? (Blue Angel?)
Click to expand...
Click to collapse
Should theoretically work for all HTC devices.
Only have an HTC Diamond to try it myself, but others tested it on Universal, HD, Raphael, ...
Nice to see you back Bepe!, Happy New Year
OMFG
bepe, you've completely outdone yourself this time!!! Checked out the videos, looks amazing!! Congratulations.
Downloaded, will check it out and post results. Thanks!!!
Hmm.it will work on all htc devices.
maybe some older dev cant use,need to test by yourself
really nice Rom Kitchen.
Great jod!!!
Cheers
Monkeybape
i second the post with the video tutorial !! great work and even me is able to build a rom now *lol*
Is removal of unneeded files from XIP supported, bepe??
this look fantastic bepe, as usual
even though I have tested it, I noticed two things:
1. Wouldn't replacing WINCE_NLS in the XIP from a different device, let's say, cause the phone not to boot?
2. What if the device you are porting from has a different resolution, wouldn't you have to change the files in the SYS manually?
other than that, it looks GREAT!
thanks again
chavonbravo said:
Is removal of unneeded files from XIP supported, bepe??
Click to expand...
Click to collapse
yes, it possible to add/remove all files/modules you want. It works the same way as in IMGFS... just delete the file/module from the XIP package or add a new one to an existing or new package.
the Kitchen will not include files that are not needed like boot.rgu, *.rgu, *.dsm to the XIP section, so there is no need to remove them after the XIP partition is build.
mbarvian said:
this look fantastic bepe, as usual
even though I have tested it, I noticed two things:
1. Wouldn't replacing WINCE_NLS in the XIP from a different device, let's say, cause the phone not to boot?
2. What if the device you are porting from has a different resolution, wouldn't you have to change the files in the SYS manually?
other than that, it looks GREAT!
thanks again
Click to expand...
Click to collapse
1. replacing WINCE_NLS is not really a problem, but the size of the .nls file might be.
example:
- you are using a WWE Kitchen with a WWE nls size: 267 KB
- you want to change lang to CHT, the nls size would be 1500 KB
--> this means the size of the xip section would grow very much
--> ROM\os.nb.payload is WWE and would not have enough space for the bigger CHT XIP
--> ImplantXIP.exe should give you an error I think... never tried it...
solution: use the CHT os.nb.payload (just replace the WWE .\ROM\os.nb.payload by the CHS one)
The CHS roms would have more space for XIP, so all would be working fine
2. Using another resolution is not a good idea... most SYS packages are compatible, but there are packages like this:
- Base_DPI_192 - this is for 192 DPI like Diamond, Raphael, HD
- Base_DPI_96 - only for QVGA devices
- base_dpi_192_resh_480_resv_640 - this package tells you the exact resolution it was made for
You could mix two builds, like using only new packages without *_DPI_192 or *_dpi_192_resh_480_resv_640 in the name...
... but not really a good idea, even that many ppl are making that. Consider that there might be resources that might be changed
Would take a look at it, but the forum requires compulsory registration to view.
Please fix your forum.
It tells me I'm missing msvcr71.dll when I try and dump. I noticed that file is other kitchens so I tried to copy it over and it starts the dump but then RecMod.exe stops responding and it asks to close.
I keep getting this error when it comes to running platformbuilder
Code:
This aplication has requested the runtime to terminate it in an unusal way
boo, I wanted to watch the tutorial on your forum again, getting an initflashfiles .dat not where it's supposed to be error. but your forum seems to be down, or under too high traphic right now, is there any way you would think of putting together a short text based info set on everything we need to know to dump and rebuild? if not, no biggie, I am sure I will figure it out, like any great new tool, there is always a learning curve Thanks much for sharing your work with all of us though
Good to see you back bepe!!! I will give this a shot later on today...
outstanding bepe!! I thought your tutorials were excellent too!
thanks bepe
tested your kitchen on my Elfin and it worked well except for implantxip, because i've reduced the size of my XIP partition in template payload, so implantxip gave me error like "no xip section found". i replaced implantxip with msflshtool and it worked fine. no other issues faced in ROM building and porting newer build for my Elfin . although i had to make some adjustments to Dump_200.bat for dumping the ROM.
also, we used buildxip for xip porting before and it had some specific switches like -g, -k and -f useful for enabling different kernel modes, changing fsrampercent etc. i was wondering if same is possible while xip porting with new kitchen or is the best setting chosen automatically?
and, do check your paypal for Transaction ID: 45A49499TS934251W
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