A kitchen of a cleaned Sprint's 3.35.651.2
running WM 6 CE OS 5.2.1629 (Build 18136.0.4.8)
(no radio included -- requires 3.35.04, 3.37.20, 3.39.10)
With the release of 1.3.0 I think that this project may be complete.
I can't think of how to safely free up any more memory and every module
that I had planned is packaged separately into the kitchen.
Small additions may come but I can't foresee any major revisions.
Using DogGuy's Kitchen Maker this was originall based off of a1jatt's preliminary cleaning of the official Sprint release, v1.3.x is a direct cleaning of the 3.25.651.2 OS ROM.
I have packaged the latest official Alltel, Sprint, and Telus carrier setups, with the rest from DCD.
The base (with Office) of this kitchen installs a ROM at 49 MB and when first after boot providing ~25.6 MB of RAM free at the default 6 MB pagepool:
OEMizer & PagePool Changer utils are included for you to customise your ROM further.
Carriers:
Alltel (settings from the April/08 release), Bell, Cricket, QWest, Sprint (settings from March/08 release), Telecom, Telus (settings from the July/2007), Verizon
Removed:
.NET CF 2.0, HTC Guardian, SQM, HTC Home, HTC Task Manager, Adobe Acrobat
Cyberon Voice Speed Dial, Esmertec Java, remaining items of Sprint Navigator, Lockstream DRM, Windows Live, Office
Kitchen:
Except for the rotten HTC Guardian, the kitchen includes all of the removed
apps and utils, plus some fundamental choices for tweaks,
dotFred's Task Manager & Registry Editor, Oxios Memory, SIPChange,
and No2Chem's nueLED 1.5 & nueAudio 1.0,
Remote Desktop, Today Screen Disable Options, UC Compatibility auto-run after first boot,
choice of the newer .NET CF 3.5 or .NET CF 2.0 as included with the Sprint ROM,
Office, OneNote, Windows Live, DCD's standard registry tweaks....some games..., HTC Zip, Touch Dialer,
Esmertec Jbed 20080222_3_1, Esmertec Jeodek 20080115_4_1 (read here for info on differences)
- you may add your own to the Kitchen's OEM directory.
This kitchen package is released to be a small and stable base for the OS.
Follow to this XDADeveloperWiki page for links to many OEM packages for you to
collect and apply the individual items that you wish to build into the ROM.
MIRRORS:
v1.3.2
http://www.megaupload.com/?d=5VR5SV7S
http://www.mediafire.com/?mawzy1wp5dn
v1.3.1
http://www.mediafire.com/?ehydfqjwtyc
http://www.megaupload.com/?d=A457KYNF
v1.3.0
http://www.mediafire.com/?llebzi2snvd
http://www.megaupload.com/?d=M6X685I0
v1.2.5.1
http://www.mediafire.com/?djyuznmmmtn
http://www.megaupload.com/?d=5IKSTCCX
v1.2.4
http://www.mediafire.com/?jzyyoem1zn2
http://www.megaupload.com/?d=LGSDOOL3
THANKS GOES TO:
DCD, a1jatt, No2Chem, and DogGuy for his excellent kitchen utility!!!
~~~~~~~~~~~~~~~~~~~~~
Easy installation:
HINT: Avoid hassles with your USB connection and PC by flashing via a non-SDHC microSD card
This ROM requires Olipro 2.40 bootloader
If flashing ROMs via the microSD method then update to 2.40 before continuing on.
radio 3.35.04, 3.37.20, or 3.39.10 is required
via the microSD card flashing method (below), upgrade your Titan directly to the radio without reflashing the OS or via the full Sprint 3.35.651.2 ROM (radio 3.35.04) or Alltel 3.35.671.9 ROM (radio 3.37.20) or Sprint pre-release 3.49.xx (an executable archives, right click to extract the RUU_signed.nbh ROM file)
Use the SD card method to only flash the CDMA radio to 3.37.20 or 3.39.10
Flash to one of the latest Sprint or Alltel ROMs but do NOT boot into the OS after flashing to this ROM.. Carrier specific customisations will run after screen calibration and alter your EPST settings.
Repeat the microSD flashing routine to flash to the kitchen built ROM.
I. OEMizer (optional)
Run OEMizer.exe from the kitchen's tool directory.
Complete your choices to customise your Titan's OS/Owner/Data/etc configurations
Hit the 'Create OEM' buttom for the customizations to be written into the kitche's OEM directory.
Build your ROM via the kitchen.
II. Kitchen
Run BuildNB.bat to execute BuildOS.
Hit the play button when you have selected your choices.
Exit BuildOS once it has completed.
Let the batch file complete its jobs.
quit the ROM Upgrade utility when it loads up and skip onto the following instructions on how to flash via the microSD card method.
OR follow through to finish the flash with the ROM Upgrade Utility via the USB.
III. PagePool Changer (optional)
Run PagePool Changer.exe
Select your ROM -- /RUU/RUU_signed.nbh
The default is 6 MB
The Titan has limited RAM so it isn't recommended to go beyond 8 MB
go smaller if you want more RAM free
Hit 'Close' when ready.
Flash your custom ROM.
IV. Flashing via a non-SDHC microSD card
With a card reader on your PC, format a non-SDHC microSD card into FAT32 (tested to work up to a 4kb cluster size)
From the kitchen's RUU directory, copy the ROM (RUU_signed.nbh) to the root of the microSD
Rename the ROM to TITAIMG.nbh
Insert your card.
Force into the boot loader with POWER-CAMERA-RESET
Follow the instructions and you'll quickly flash your Titan...
This will work to flash with an official ROM and radio, I think regardless of the boot loader you have installed. But ensure that you have the correct boot loader (olipro 2.40 for this ROM) installed for when you do eventually finish with your flashing and are ready to boot into the OS.
change log
Known issues: nada
~~~~~~~~~~~~~~~~~~
v1.3.2 [23/04/08]
Updated Alltel carrier settings to the that of the April/08 Alltel 3.35.671.9 ROM
Alltel specific Arcsoft MMS settings -- waiting for those on alltel to test
Updated from the new Alltel ROM:
bluetooth drivers BTHCI.dll
CDMA_API.dll
InitProv.dll
v1.3.1
updated Sleuth255's UC to v2.0
Choice between the stock and Touch camera
Choice between the old (stock jeodek) and latest Esmertec Jbed 2008/02/22 Java (apparently you may install both -- read here for info on differences)
Changed mxip_notify.vol to remove any Customer Feedback reminders
Customer Feedback link in settings is removed by default without the need to select DCD's common registry tweaks
v1.3.0
Fully cleaned remaining SQM bloat...well, except for the customer feedback link in system settings.
Finally OEM'd the stock dialer so dialer skins are now supported by the kitchen - fttilt's Touch dialer is included
Sprint is now using nearly identical operators settings as the official ROM
The missing '1' in the stock dialer when using Sprint is resolved.
v1.2.5.1
Back to the stock AudioPara.csv only. The available modifed ones are incompatible with the profile of SPB PhoneSuite and tend to lock up the device. They're for WM 6.1 only? I may include a working option from one created with nueAudio within WM 6, but you can include nueAudio into the build and quickly personalise the handset and 'earcuple' settings within the OS.
v1.2.5
Customer feedback and SQM is removed.
Removed Office, OneNote, and Windows Live and added their options to the kitchen.
Added a choice of Scrufdog's louder AudioPara.csv (tested and works with SPB Phonesuite) or the stock file from Sprint.
Added the option of DCD's regular ROM tweaks.
Were previously bundled into the SYS directory by a1jatt.
v1.2.4
Removed Lockstream DRM as it was prompting issues with the PRL and slow boots.
Returned .NET CF 2.0 as per the Sprint ROM providing the choice between that OR the latest 3.5
v1.2.3
A choice of Comm Managers is now possible
Included the popular 10 button manager
Removed the modifed audiopara.csv and replaced it with the stock file.
It was interferring with SPB Phone Suite's profiles
v1.2.2
Changed the .NET CF 3.5 package to the one included in _Alex_'s v5.1 OEM pack.
Removed the Lockstream DRM files and added it as a kitchen option.
Kitchen additions:
FTouchFlo, FTouchFlo Config, Remote Desktop, and Today Screen stock item disable options.
v1.2.1
I was wrong, it was not .NET 3.5 that was causing the trouble but No2Chem's battery .dll was somehow preventing apps from seeing/accessing COM4.
the battery dll is back to stock.
.NET CF 3.5 is back in and 2.0 is once again removed.
v1.2.0
to resolve VisualGPSc not seeing the GPS's COM4, I removed .NET CF 3.5 and reverted back to Sprint's stock 2.0
removed No2Chem's nueAudio from the kitchen as it requires .NET CF 3.5
v1.1
Added carrier selections
Telus based services from last summer's WM6 offical release
Remainder carriers from DCD's releases
Removed Adobe Acrobat Reader
v1.0
My FIRST ROM/kitchen!
Thanks Key... downloading now. I've been looking to cook a custom TELUS ROM with WM6 and drivers that support the new radio.
FIRST IMPRESSIONS:
- Very Speedy ROM overall
- initial free RAM is ~24 as claimed
- I still think an 8MB pagepool is a must for the TITAN so it was nice to still be able to do a custom PP with this kitchen
- Sprint Customization forces carrier back to SPCS. Is there any fix?
- additional OEM dialer skins, smart dial, calc (vogue) would be nice to cook with as well
- Some things like "get good" still need to be removed
Looks like the kitchen still needs some work at the moment. Flashing back to DCD 3.0.1
Would you consider swapping out the extended rom driver with the one in no2chem's rom so that the extended rom can be unlocked. Also, does your rom work with wm5torage. If not, could you add an option to swap the memory card driver with a previous version that does work with wm5torage.
Thanks for the great work. I'm already downloading your rom!!!!
- Sprint Customization forces carrier back to SPCS. Is there any fix?
SO could I be using this as a functioning 3.35 Sprint kitchen? That's what I am really in search of... Thanks,
Josh
Juicy47 said:
- Sprint Customization forces carrier back to SPCS. Is there any fix?
Click to expand...
Click to collapse
Should be resolved now. The ROM this was based upon wasn't fully set-up for Telus and still had some of the previous Sprint settings in the OEMOPERATORS folder. That's all history with the use of DCD's selectable carriers. As it appears DCD did with his Sprint and Verizon settings, hopefully all is fine with my reversion from DCD Telus settings to the official operator settings from last summer's Telus WM6 release.
Juicy47 said:
- additional OEM dialer skins, smart dial, calc (vogue) would be nice to cook with as well
Click to expand...
Click to collapse
For now I just wanted to get this out clean and working. I haven't had a chance to test for skins yet.
Juicy47 said:
- Some things like "get good" still need to be removed
Click to expand...
Click to collapse
I was disspointed by that too... Anyone know the names of the associated files?
Juicy47 said:
Looks like the kitchen still needs some work at the moment. Flashing back to DCD 3.0.1
Click to expand...
Click to collapse
Thanks for helping! I'm learning. Now I will get onto last night's odd COM4 mystery with VisualGPSc.
atomclock said:
Would you consider swapping out the extended rom driver with the one in no2chem's rom so that the extended rom can be unlocked. Also, does your rom work with wm5torage.
Click to expand...
Click to collapse
I did consider that but I wanted to keep things as simple as possible. You're welcome to add it.
Keystone said:
I did consider that but I wanted to keep things as simple as possible. You're welcome to add it.
Click to expand...
Click to collapse
I would be happy to make the changes. Would you mind telling me where you learned how to change the .net version from 2 to 3.5. I tried doing this using dog guy's kitchen and the original rom image and while i had limited success it was really only a cludge which is kind of buggy. long story short, i dont know how to modify the underbelly of the rom which wold be necessary to change the drivers. if you can give me a link or a brief explanation of the process then i will be happy to work out the details of this mod.
thanks
atomclock said:
I would be happy to make the changes. Would you mind telling me where you learned how to change the .net version from 2 to 3.5. I tried doing this using dog guy's kitchen and the original rom image and while i had limited success it was really only a cludge which is kind of buggy. long story short, i dont know how to modify the underbelly of the rom which wold be necessary to change the drivers. if you can give me a link or a brief explanation of the process then i will be happy to work out the details of this mod.
thanks
Click to expand...
Click to collapse
I deleted the net directory within the SYS directory. Then I added the PPCGeeks OEM of 3.5 to the OEM directory of the kitchen.
I have since removed it and gone back to 2.0, as 3.5 alone was giving a single odd error of VisualGPSc not being able to recognise COM4 for the internal GPS. I'm not sure if it was the GPS driver, VisualGPSc, etc., that was having the issue but since 2.0 fixed and I didn't know what other problems 3.5 may cause, I've gone back to the .NET settings that Sprint released.
Thanks for the offer for the carriers, but I was quicker than I expected! All done.
As for learning, I began last night at 10 on a whim of wanting a cleaned version of the Sprint WM6 release for myself. I had the weekend free so all last night I went for it.
Keystone said:
I deleted the net directory within the SYS directory. Then I added the PPCGeeks OEM of 3.5 to the OEM directory of the kitchen.
.
Click to expand...
Click to collapse
This is the same thing I did but it causes errors with some .net applications. If you look at DCDs roms, the SYS/NET directory is replaced by a SYS/NET35 directory. (Note, you can't just replace the directory it doesn't work) In other words, he integrates net35 into the rom instead of using an oem. I believe that there is a place where the registry keys are hiding but I can't find them. The only glimpse I have had of these hidden registry keys is when you do a partial build of the rom and then extract the user.hv and default.hv files. Then you can see the registry keys. Unfortunately, modifying the registry keys at that stage of the build is not really practical because it would have to be done every time the rom is built. I was hoping you had done the integration similar DCD and that you might share you knowledge. I have searched and I can not find the information.
Thanks again for you work!
P.S. By the way, if I ever learn how to do this I am planning on modifying a WM5 kitchen with the latest drivers and gps so that I can reduce the memory footprint.
atomclock, I dunno but since I found that .net 3.5 wasn't at fault for the GPS and I haven't crashed other apps, I think that I will leave it in. If people notice problems then it will be a quick change for me to revert back to 2.0 in the kitchen.
We may get word from DCD and others as to what and how things are working for them.
thank you!
d/l now. i have to let the phone charge up a bit and then will try out your rom. What are the advantage of the 3.5 framework again?
I am currently running the factory rom cause dcd's version would not let me connect to the net after a period of time.
Juicy47 said:
Thanks Key... downloading now. I've been looking to cook a custom TELUS ROM with WM6 and drivers that support the new radio.
FIRST IMPRESSIONS:
- Very Speedy ROM overall
- initial free RAM is ~24 as claimed
- I still think an 8MB pagepool is a must for the TITAN so it was nice to still be able to do a custom PP with this kitchen
- Sprint Customization forces carrier back to SPCS. Is there any fix?
- additional OEM dialer skins, smart dial, calc (vogue) would be nice to cook with as well
- Some things like "get good" still need to be removed
Looks like the kitchen still needs some work at the moment. Flashing back to DCD 3.0.1
Click to expand...
Click to collapse
Did you try going over 8MB with the pagepool and see what effect it had on free RAM after bootup? I'm running a 24MB pagepool on a Touch and the larger size makes a world of difference.
atomclock said:
I would be happy to make the changes. Would you mind telling me where you learned how to change the .net version from 2 to 3.5. I tried doing this using dog guy's kitchen and the original rom image and while i had limited success it was really only a cludge which is kind of buggy.
Click to expand...
Click to collapse
I'll soon repost a link to download my v1.2 that uses CF 2.0 rather than 3.5.
Hmm, I keep crashing BuildOS.exe when running the batch. I have all the packages as DCD suggested, and can cook other ROMs just fine.
Any ideas what might cause this?
If there is an NBH file in the RUU folder (from previous cook), that will block the BuildOS. Delete it if it is there.
morganlowe said:
Hmm, I keep crashing BuildOS.exe when running the batch. I have all the packages as DCD suggested, and can cook other ROMs just fine.
Any ideas what might cause this?
Click to expand...
Click to collapse
I'm sorry morgan, but few ideas.
Are you extracting the archive of the kitchen to a fresh folder?
Do you have appropriate security rights for the folders?
Are you running BuildNB.bat intact and unmoved from there?
When does it crash? Upon loading BuildOS or when BuildOS dumps the new OS to its created TEMP directory?
Well, I configured my OEMs, added a few of my own. It's fully extracted in it's own folder inside my 'phone' folder. I have all the rights. I did not change any of the files after unzipping.
It crashes right as I run the batch, when it goes to load buildOS...
http://www.morninglion.com/crash.jpg is a screen shot.
Just a guess, but do you have the latest MS Visual C++ Resdistributable installed?
Yup, and all the latest .nets... I do all my ROM building on this same PC, this is the only one to give me an issue... Maybe it's the mirror I used, let me try another.
Related
dcd's kitchen 1.6.10
Carrier support for sprint, vzw, bell, telus, alltel, qwest. No instructions included yet.
Updated WM6 OS: CE OS 5.2.1622 Build 18128.0.4.4
Pagepool is 5mb because I feel it is the best for titan. If you wish to build for other pagepool sizes, use this.
OEM Based (mostly) on RUU_TITAN_SPRINT_WWE_2.17.651.0_RS_TITAN_SPCS_1.47.01_Ship.exe
All OEM applications incoluded. No additional applications included.
Download:
1.6.10
Although I still consider this a test, some people may want to use it to build and distribute their own stuff. If you would please just mention my name it would be nice
Changelog:
1.6.10
- 01-15-08 removed package OEM_HTC_Camera_4_05_26938_00
- 01-15-08 added package OEM_HTC_Camera_5_07_28987 (no flash!!)
- 01-15-08 replaced webview.dll in BROWSING package
- 01-15-08 replaced wavedev driver with Vogue 1.17 version
- 01-15-08 updated package AdobeReader to 2_00_288531
- 01-15-08 added package OEM_HTC_StartupAnimation
1.6.9
- 01-03-08 changed package dcd - remove conflicting kb backlight autosensor entry
- 01-03-08 changed package dcd - clean up
- 01-03-08 added package OEM_VoicemailTodayPlugin
- 01-03-08 added package OEM_dcd_carrier_none
- 01-03-08 buildos defaults now have no certain carrier in mind
- 01-03-08 renamed Optional_* to OEM_*
1.6.8
- 12-27-07 changed package Optional_Dialer_VogueClone - new dialer images (cleaner, background)
- 12-28-07 changed package OEM_Driver_USB_2_17 - include missing reg keys per sd_matto
- 12-28-07 changed package Optional_JbedJava_Sprint_20070828_4_1 - include shortcut per sd_matto
- 01-01-08 changed package OEM_Lockstream_DRM_1_1_x_070209_R1 - fix guid, no longer included unless checked
- 01-01-08 changed package dcd - disable keyboard backlight autosensor
- 01-01-08 changed package dcd - copy RDP cache tweaks from 'wpctsc', will now remain if others port SYS
- 01-01-08 removed package Optional_HTC_Smartdialing_v28536_Vogue - not working, not needed, screw it.
- 01-01-08 replace packages Browser, MediaOS, WindowsLive, RDP (internal testing 18508.0.7.0 ver)
- 01-01-08 clear some dsm files, rom dump now rebuilds correctly
- 01-01-08 remaining oem stuff in initflashfiles.dat split out to initflashfiles.txt in individual packages
Can't wait to try it.
Stupid rapidshare and their qeues.. I want this now, not in 42 mins.. lol!
Seriously can't wait to try this out!
Did you mean for the nbh to be placed in the main folder and not in the RUU folder to run automatically? I had to move the nbh and run the RUU seperately.
Very cool! Thank you for all the work that you put in on this stuff, dcd! I had no problems with the last release and look forward to giving this one a go.
blazingwolf said:
Did you mean for the nbh to be placed in the main folder and not in the RUU folder to run automatically? I had to move the nbh and run the RUU seperately.
Click to expand...
Click to collapse
yes. move it over, or do whatever it is you do with it.
Good stuff! Just cooked up my first ROM with this with a newer Arcsoft MMS (vzw) and some other stuff.. runs great!
dcd1182 said:
yes. move it over, or do whatever it is you do with it.
Click to expand...
Click to collapse
Ok.
Created a VZW ROM and everything seems to be running fine. Thanks for this.
Tres cool, just wondering what is in the entertainment enterprise packages. I guess I could just try it and see, but I might miss something .
jjlwork said:
Tres cool, just wondering what is in the entertainment enterprise packages. I guess I could just try it and see, but I might miss something .
Click to expand...
Click to collapse
Bubble Breaker and Solitaire for the entertainment OEM.
WyldStar said:
Good stuff! Just cooked up my first ROM with this with a newer Arcsoft MMS (vzw) and some other stuff.. runs great!
Click to expand...
Click to collapse
what newer mms package? please provide it
i cant get anythign but 3.0 to work
Not Sure if this is intentional but selecting entertainment package adds solitaire and bubble breaker to the windows directory but does not create Games folder in Program files or links to the games.
dcd1182 said:
what newer mms package? please provide it
i cant get anythign but 3.0 to work
Click to expand...
Click to collapse
There's an OEM for 4.2.8.1 here..
http://forum.ppcgeeks.com/showthread.php?t=10210
Instructions for installing it on VZW worked fine, sends and recieves. Dunno if it would work on Sprint.
Excellent work as always dcd! Modded a few things I like in the kitchen, works great!
DCD,
Thanks so much for your work! I am running your 1.6.7 and it's smooth. I was going to give the kitchen a try.
Dumb questions...
Is it really as simple as picking the options in the "BuildOS" and then running the batch file?
I am trying to figure out what some of the options are like the Enterprise component or the IA Zip. You wouldn't happen to have a readme file somewhere that I am missing would you?
Thanks again!!
jjlwork said:
Not Sure if this is intentional but selecting entertainment package adds solitaire and bubble breaker to the windows directory but does not create Games folder in Program files or links to the games.
Click to expand...
Click to collapse
oops thats my fault i bet. ill fix
robbyr said:
DCD,
Thanks so much for your work! I am running your 1.6.7 and it's smooth. I was going to give the kitchen a try.
Dumb questions...
Is it really as simple as picking the options in the "BuildOS" and then running the batch file?
I am trying to figure out what some of the options are like the Enterprise component or the IA Zip. You wouldn't happen to have a readme file somewhere that I am missing would you?
Thanks again!!
Click to expand...
Click to collapse
yeah its really that simple. those are wm6 packages, i will include a readme eventually but for now its as-is.
WyldStar said:
There's an OEM for 4.2.8.1 here..
http://forum.ppcgeeks.com/showthread.php?t=10210
Instructions for installing it on VZW worked fine, sends and recieves. Dunno if it would work on Sprint.
Click to expand...
Click to collapse
thats interesting, ive never been able to get it to work on sprint. maybe i should use this for the vz rom instead of 3.0.
Love the memory after reboot!
Only issue I'm having is I tried to send a picture mail and it won't send, it keeps failing. I didn't change any picture mail settings and everything "looks" correct.
Here I have a bunch of boring ROMs for your StarTrek. I call them boring because they are devoid of any personalization, customization, or 3rd party apps other than what comes with a shipping ROM. These ROMs are OS only, will not change your initial splash or radio (but it does change the operator splash). A text file ReadMe.txt in the download contains brief instructions on how to flash this ROM. Apparently the 3.06 IPL/SPL in QTEK ROMs is broken and cannot recover via MicroSD so I would recommend updating to 4.01.0001 prior to flashing any of these ROMs, although that in itself can be risky (see below for download). Enjoy, and flash at your own risk!
Details
5.2.1711 (Build 18170.0.5.1) Core OS (SYS) is ported from T-Mobile Shadow Feb. '08 update.
OEMAPPS and OEMOPERATORS are straight from CWS 4.1.502.5 ROM. It has the latest camera and apps.
OEMDrivers specific to StarTrek are the latest, from 4.1.502.5 ROM. Some common libraries are from TMO Shadow ROM.
OEM Edition for AT&T 3125 - The same old, boring, Cingular-branded ROM you're used to, only ported to WM6. My objective with the Boring Edition is a ROM that's indistinguishable from what an OEM would put on a shipping device. This is based on Cingular ROM v4.1.502.5 with many changes made throughout to work with the WM6 core, but hopefully the changes are transparent. It comes with all the bloatware and apps that came with the original Cingular ROM. If you want lots of storage and free RAM, this is NOT the ROM for you!
Adobe Reader LE 2.0 (new, from TMO Shadow, replaces original ClearVue PDF)
Office Mobile (new, replaces original ClearVue Office suite)
Windows Live/Live Messenger (new, replaces original MSN Messenger)
Microsoft Voice Command (replaces Cyberon Voice Dial)
English-only xT9 (new, from HTC S730 "Wings", dated Sep 7, 2007, replaces older T9)
Esmertek Java (new, from TMO Shadow update, replaces discontinued Tao Intent Java)
Cingular bloatware, customization, setup, and theme
Clock/carrier block of Cingular theme changed to standard WM6 style (I liked the bigger clock).
SecurityOff (required, because some apps can't install with it on)
Clean ROM WM6 - Similar to the above (same drivers), but lacking Cingular customization and bloatware. Does NOT have Microsoft Office or Adobe Reader. This will leave more storage available for 64MB devices like QTEK 8500 or iMate Smartflip. As this is an unbranded ROM, you will need to manually set up your GPRS and Proxy connections.
Windows Live/Live Messenger (new)
English-only xT9 (dated Sep 7, 2007)
Esmertec Java
Cyberon Voice Dial
SecurityOff (required, because some apps can't install with it on)
Neo Edition Clean WM6 ROM - Same as above, only added Neo theme from the T-Mobile Shadow. No other customizations.
CREDITS
Thanks to pArtizAn (Erofich), Alex[DFR], Strik3r, and Chymmylt for use of the WM6 XIP in early versions of my ROMs. Without it, my first ROM would have been delayed 2-3 weeks.
Known Bugs - Applies to all versions.
Analog Clock 2 and Analog Clock 3 on external display don't look right. NOT a WM6 bug because the original Cingular WM5 has the same problem!
Possible xT9 can't backspace on some websites bug.
Roll your own! Here are the SYS, OEM, and ROM folders for the Clean Edition ROM. Add this to your favorite kitchen. RUU included.
For experienced ROM builders only!
Download Clean Edition Kitchen files
Other Updates
These are from the latest Cingular ROM, newest for STARTREK that I'm aware of. I have tested these and they worked fine on my phone but I am not responsible if you take the risk and they damage your phone! Flash at your own risk!
Download IPL/SPL 4.01.0001 CAUTION: Flashing IPL and SPL could kill your phone... permanently!
Download Radio 4.1.13.34_02.79.30
Download Radio 4.1.13.46_02.97.90
Prerequisites
Your device must be CID unlocked! See this thread.
Please report any bugs with a detailed explanation of how to reproduce them.
Change Log
Mar 6, 2008 - OEM version, single press of RECORD button activates Voice Command. Should support BT activation now. All clean versions now use the same animated HTC splash. Shows HTC logo on outside screen instead of blank (thanks Erofich). I figured how to port XIPs so all ROMs now use my own XIPs ported from scratch. Added Neo and WM6.1 editions.
Feb 21, 2008 - Fixed Vibrate in Profiles bug, possibly fixed Microsoft Live can't connect bug, updated some files (no longer have to press OK after cold boot setup), newer OS build (18170.0.5.1), newer Esmertec Java, Sim Manager, changed Cyberon Voice Dial to MS Voice Command on Boring version.
Feb 18, 2008 - Changed Tao Intent Java to Esmertec Java, T9 to xT9 on all versions. Added download links to latest radio and IPL/SPL.
Feb 16, 2008 - Added kitchen files for Clean Edition.
Feb 15, 2008 - Added Clean Edition. Changes to Boring Edition: T9 problem fixed, Start menu now allows scrolling (no need to press More), SecurityOff to fix programs can't install problem.
Feb 13, 2008 - Original Release of Boring ROM.
Click to expand...
Click to collapse
Extras
Clean ROM a little too clean? Here are some add-ons in CAB form.
Adobe Reader LE 2.0 Build 288531 (from T-Mobile Shadow)
Neo Black & Blue Theme - Only works on ROMs with Neo integrated. Not just a simple color change, I tried to copy the mockup of T-Mobile Black. It looks almost identical to the mockup on my PC, but unfortunately the conversion from 16.7m to 65k colors results in some false contouring.
thanks man!!
does gprs work in this one?
GnatGoSplat said:
Boring ROM WM6 Cingular (AT&T) - It's the same old, boring, Cingular-branded ROM you're used to, only ported to WM6. My objective with the Boring ROMs is to make a ROM that's indistinguishable from what an OEM would put on a shipping device. This is based on Cingular ROM v4.1.502.5 with many changes made throughout to work with the WM6 core, but hopefully the changes are transparent. It comes with all the bloatware and apps that came with the original Cingular ROM. If you want lots of storage and free RAM, this is NOT the ROM for you!
XIP is thanks to Erofich's WM6.
5.2.1711 (Build 18165.0.5.0) Core OS (SYS) is ported from T-Mobile Shadow.
OEMAPPS and OEMOPERATORS are straight from CWS 4.1.502.5 ROM. It has the latest camera and apps.
OEMDrivers specific to StarTrek are the latest, from 4.1.502.5 ROM. Some common libraries are from TMO Shadow ROM.
Changes
Behind-the-scenes changes were numerous, but visible changes are minimal (although I did make a few):
Office Mobile replaces ClearVue apps. Most devices that used ClearVue in WM5 were changed to Office Mobile in WM6 so monkey see, monkey do.
Adobe Reader LE 2.0 from TMO Shadow replaces ClearVue PDF.
Clock/carrier block of Cingular theme changed to standard WM6 style (I liked the bigger clock).
Known Bugs
Analog Clock 2 and Analog Clock 3 on external display don't look right. NOT a WM6 bug because the original Cingular WM5 has the same problem!
OS only, will not change your initial splash or radio (but it does change the operator splash).
Download
Please report any bugs with a detailed explanation of how to reproduce them.
If there is much interest, I can make a cleaner, unbranded version of this ROM or a vanilla kitchen.
Click to expand...
Click to collapse
Will this work on i-mate SmarkFlip (out of box device without any hacks)
Yes, GPRS works, but I use T-Mobile so I had to add a connection to T-Mobile GPRS. It should work with Cingular/AT&T as-is.
It should work on a SmartFlip, but I'm not sure if you need to CID unlock first.
Downloading and installed...
Attempt 1: Read everything within the Word file. Installed right from the RomUpdate program in the root directory of your
WM6 update. Didn't work, so I will attempt what you have in the Readme text file in my next attempt....
Attempt 2: The Update Utility program says version 3.12.3.1 on the title while the pictures you have in the word file says
version 2.99. Also, when I go through to update ROM, it verifies my current Image version as 4.1.502.5,
I click Update and the next screen it indicates that it will be updating from my current version to the
new version of 1.00.000.0. Then, a minute or so later, I get the following message:
ERROR [270] : UPDATE ERROR Image file is corruprted. Please check your Update Utility.
Do you know how I could resolve this matter because you do not list error 270
within your troubleshooting material? Your UpDate program is not even the same version!
Vista Home, Cingular 3125 unlocked with current released Rom version. So, what am I missing here?
Sorry, I shouldn't have included the Word doc, it's the standard doc that came with the RUU and happened to be in the folder at the time.
Are you using SoftSPL? You MUST use the SoftSPL, it won't work to just run the RUU. The doc I wrote is ReadMeWM6.txt.
You also need to CID unlock according to the sticky thread.
kumar00455 said:
Will this work on i-mate SmarkFlip (out of box device without any hacks)
Click to expand...
Click to collapse
@kumar00455,
GnatGoSplat noted that this should work on any StarTrek, but there is something you should be aware of. In the past, it seems like a lot of people that have tried a Cingular ROM on a StarTrek that is not a 3125 model have not liked it, because they ended up with too little storage memory. This is because Cingular has loaded a ton of large crapware programs on their ROMs. Now, that isn't a big problem for the 3125, because it is actually different hardware from all other StarTreks - it has double the storage memory (128MB) all the other StarTreks (which have 64MB). Since GnatGoSplat has tried to make this just like a Cingular ROM, with all the added programs, you may find you have the same problem. However, I do think there is a thread here somewhere that talks about how to clean all the crapware off of a Cingular 3125 ROM and reclaim some storage memory.
@GnatGoSplat,
Thanks for putting this together - I think I will try it soon on my 3125! I would be very interested in a cleaned-up version and a kitchen as well. And of course, many thanks to Erofich and everyone else who worked on getting WM6 on the StarTrek. I thought we would never see this day!
Oh yeah, I forgot the 3125's have double the storage memory!
I'll make a slimmer, cleaner ROM as soon as enough people have tried this one to confirm it doesn't have any significant problems.
What apps are essential to keep in a cleaner ROM and which can go? What are typical apps that come on a Smartflip or 8500?
device PIN lock working?
Can anyone who has tried this ROM tell me if the security PIN lock works correctly without any problems? I sync my 3125 with my corporate Exchange server, and our IT people enforce a device PIN lock requirement through the Exchange server. So I have to enter a 6 digit PIN if the phone has been idle over an hour. Anyway, I'm interested in flashing this ROM, but if there is any problem with that functionality in this ROM, it would be a deal-killer for me... Thanx...
GnatGoSplat said:
Oh yeah, I forgot the 3125's have double the storage memory!
Click to expand...
Click to collapse
I do like your approach here, though. Start with something as much like the carrier ROM as possible until you know that it's pretty stable, then put it on a nice diet to make it lean and mean. Makes good sense to me...
GnatGoSplat:
i am in china. so i download this file so slow,can you send to me ?my e-mail:[email protected]
SoftSPL
Ok I'm where do i put the SoftSPL file and how do i use it. i tried putting it in Windows directory nothing. please help i really want to get WM6 on my 3125
guyver76 said:
Ok I'm where do i put the SoftSPL file and how do i use it. i tried putting it in Windows directory nothing. please help i really want to get WM6 on my 3125
Click to expand...
Click to collapse
Put it in the root of your device /not/ Windows. Start softspl.lnk as it says in the manual
I tried to use the program you directed the user to transfer. Everytime I clicked on it, I would get an error which stated that the link's program could not be found.
Don't get me wrong over here, I read the directions a few times and did everything you instructed. I am pretty good with directions and I am not one for doing things my own way. If I could help in anyway, just say something. I have alot of times on my hands and I am educated in matters, like, programming on my home desktop.
I made several attempts, I still get the same error, time and time again.
Are you trying to run the correct SPL? The one that looks like a square with a blue bar on top is the correct one. The one that looks like a piece of paper with the corner folded and a Microsoft icon in the center is NOT the right one.
Also, copy ONLY the files and NOT the whole folder. All these files need to be on ROOT folder of your device. If you're using ActiveSync, when you open your device icon, it defaults to My Documents so you have to go to My Device.
Okay, there we go. I copied the entire folder. Sorry. :O(
I'll make a new attempt in just a few.
UPDATE: I tried it, and now instead of an error, it just doesn't do anything. Sorry.
GnatGoSplat -
Thanks man, this ROM has been perfect so far. Just like my previous cingular rom with WM5. You did a superb job. This is just what I was looking for. Thanks Again!
I am waiting for the slimmer ROM since my device is teh European QTEK 8500. I am waiting impatiently
Churchill said:
I am waiting for the slimmer ROM since my device is teh European QTEK 8500. I am waiting impatiently
Click to expand...
Click to collapse
Its worth the wait!!
Thanks
Thanks for the reply i got it working now
DCD if you dont like what im doing just tell me to delete this post and i will.
All credit goes to DCD one of the best kitchen and Rom maker's out there.
If it wasn't for him our 6800's would be almost useless.
This is for the people who are using the titan kitchen. I took DCD's latest build and repackaged it for the PPCKitchen.org Titan Kitchen located
here http://forum.ppcgeeks.com/showthread.php?t=23206
Place it in your BuildOS/Kitchens directory and then extract "Titan_DCD_3.01_Selections.txt" and place it in the BuildOS/Projects directory.
Now you can create your own custom DCD rom using the new kitchen and DCD's latest build.
I've been using this for about 20 hrs and the rom is very stable.
Thanks again DCD u Da MAN!!!!!!!!
Make Sure to remove---> _fixed <---from the end of the file before u place it in the kitchens folder.
Download
http://rapidshare.com/files/108106961/Titan_DCD_3.0.4_FIXED.rar REALLY FIXED this time LOL
thank i'm looking for this. I ran into error error nk.dat
AstronusX said:
thank i'm looking for this. I ran into error error nk.dat
Click to expand...
Click to collapse
Sorry i forgot to change it from os.paylod to nk.fat, im up loading a fix right now thanks.
Errors in PPCkitchen
King - Thanks for putting this together
Unfortunately, I'm getting an error message (a bunch).
I downloaded the main file and did the updater.
When I go into BuildOS and select DCD 3.0.4 5054 or 5060, I am bombarded with error messages "Internal Error - Option.xml GUID not found (PROGRAM - xxxxxxxxxxxxxxxxxxxxx) where the "Program" is the name of the program and the x's are registry keys.
After I click ok 100 times to get through to the Kitchen, it allows me to select programs and build the OS, but once I install it, nothing actually gets installed on the phone.
Do you know what is causing this? Any help would be appreciated.
Thanks,
mfrish said:
King - Thanks for putting this together
Unfortunately, I'm getting an error message (a bunch).
I downloaded the main file and did the updater.
When I go into BuildOS and select DCD 3.0.4 5054 or 5060, I am bombarded with error messages "Internal Error - Option.xml GUID not found (PROGRAM - xxxxxxxxxxxxxxxxxxxxx) where the "Program" is the name of the program and the x's are registry keys.
After I click ok 100 times to get through to the Kitchen, it allows me to select programs and build the OS, but once I install it, nothing actually gets installed on the phone.
Do you know what is causing this? Any help would be appreciated.
Thanks,
Click to expand...
Click to collapse
Is this your first time using the kitchen?
King_tee - I had to do alot of editing to get ALL the errors to go away. I had to remove the welcomehead96.png, also had to remove a few other items.... like remotedesktop..... I guess I should have taken a log of what I did....
Edit - However - VERY nice job getting it to where it is..... Thank you
Thanks will try. The BuildOS in the regular kitchen is crashing so I can now cook a kitchen.
Also will my OEMs made for the 3.0.1 rom work if I put them in the build os directory. I didn't use the OEMizer w/ BuildOS. It appears to be the same just w/ a different save directory.
azclown said:
King_tee - I had to do alot of editing to get ALL the errors to go away. I had to remove the welcomehead96.png, also had to remove a few other items.... like remotedesktop..... I guess I should have taken a log of what I did....
Edit - However - VERY nice job getting it to where it is..... Thank you
Click to expand...
Click to collapse
No prob az i forgot about getting rid of those files. I thought i got all of them. I will upload a new file with the fixes for those who haven't downloaded it yet.
NEW FILE UP LOADED
Let me know if its working for you guys
As of this morning, the version I downloaded still gives an error (can't find HTC Sliding Sound module) when trying to load the selections.txt file for the DCD kitchen.
drgreenberg said:
As of this morning, the version I downloaded still gives an error (can't find HTC Sliding Sound module) when trying to load the selections.txt file for the DCD kitchen.
Click to expand...
Click to collapse
The sliding sounds module is in the DCD OEM's folder......when u open it up in the kitchen it should come up as a selectable OEM. At then point all you have to do is select it.
Bell?
Does the kitchen work for Bell phones? It does not seem to be in the carrier list.
jondixon said:
Does the kitchen work for Bell phones? It does not seem to be in the carrier list.
Click to expand...
Click to collapse
I don't know if it does.Are you are referring to the ppckitchen or DCD's Kitchen?
What i have provided is just a modified version of DCD's work (all credit goes to him) that will work in the ppckitchen.
You can check over here http://forum.ppcgeeks.com/showthread.php?t=23206
if you are talking about the ppckitchen, and they should be able to answer your questions.
If you asking about the DCD kitchen you can ask over here http://forum.xda-developers.com/showthread.php?t=385336 and im sure he will help you out.
I guess the obvious question is, what's the difference between the two kitchens?
DCD's kitchen is built around his ROM. The PPCkitchen kitchen isn't designed for any specific ROM or device.
Advantages of DCD's kitchen:
It's what DCD is using, so you know it builds his ROM like he intended it.
Advantages of PPCkitchen's kitchen:
Easy to install.
Prettier front end.
More error checking.
More OEMs to pick from.
Self updating.
Device dependency/exclusions supported
Carrier dependency/exclusions supported
OEM dependency/exclusions supported
Easy to move same configuration from one kitchen to the next.
Effortless switching between ROM configurations and kitchens
Splash/animation support
gguruusa said:
DCD's kitchen is built around his ROM. The PPCkitchen kitchen isn't designed for any specific ROM or device.
Advantages of DCD's kitchen:
It's what DCD is using, so you know it builds his ROM like he intended it.
Advantages of PPCkitchen's kitchen:
Easy to install.
Prettier front end.
More error checking.
More OEMs to pick from.
Self updating.
Device dependency/exclusions supported
Carrier dependency/exclusions supported
OEM dependency/exclusions supported
Easy to move same configuration from one kitchen to the next.
Effortless switching between ROM configurations and kitchens
Splash/animation support
Click to expand...
Click to collapse
I honestly don't think you give DCD enough credit for his work.... Here are some more Advantages....
Easy to use
Builds a basic ROM with only 2 clicks of the mouse.
Can be used behind firewalls.
No IP logging when you use it. (I had been told this was logged with your login name)
In all fairness both systems work very well, while the PPC kitchen has a more elegant streamlined interface, I do believe the end result is the same, a working ROM the way "I" want it.
error
hey guy anybody else getting an error unable to make file
when it goes to unpack the ppcgeeksoem rar
azclown said:
I honestly don't think you give DCD enough credit for his work.... Here are some more Advantages....
Easy to use
Builds a basic ROM with only 2 clicks of the mouse.
Can be used behind firewalls.
No IP logging when you use it. (I had been told this was logged with your login name)
In all fairness both systems work very well, while the PPC kitchen has a more elegant streamlined interface, I do believe the end result is the same, a working ROM the way "I" want it.
Click to expand...
Click to collapse
Could be because DCD has only a little to do with what we're talking about (which I gave him credit for). That's Bepe's buildos you're looking at, and essentially what we're comparing is Bepe's buildos w/ DCD integrated against PPCKitchen's buildos w/ DCD integrated.
You can't seriously suggest that Bepe's buildos is easier to use - the interface is practically identical! Both are about the same difficulty to use in their most basic, unaltered configurations, and both can build a basic rom w/ 2 clicks. Installing, configuring, starting, and maintaining is a lot different however...the nod hands down goes to ppckitchen there. Once you get past a basic configuration, PPCkitchen's buildos is unchallenged.
The proxy/firewall thing is fixed (general release this weekend) and it doesn't log IPs (never has).
Bepe's buildos get's the nod for no internet connection required, and the previous version (I don't know about v2) get's the nod for Linux compatible. Bepe's buildos also get's the nod for being more interfaceable to other projects and having more projects using it, but none of that is related to the original question (except maybe linux compatibility). [EDIT: v2 isn't native linux compatible, so no nod there.]
All of this is not too suprising, as PPCkitchen's buildos is, at it's core, an evolution of Bepe's Buildos.
I give credit to all sources DCD's kitchen / PPC Geeks kitchen and more.
They both offer the tools to make a ROM to your likings, some better then other, but the fact of the matter is that it gets the job done.
What PPC Geeks version is doing is making a bit more user friendly ( in my opinion ), but I still used DCD's kitchens because I really don't add any extra OEM's to my ROM's unless it is a specifically Themed ROM and then again I can get it done with both kitchens with ease.
I guess users will just have to test them both out themselves to see if they prefer one or the other.
What would be great is if we can have a Modifier / virtual simulator / kitchen where we can find ways to modify our ROM's / PPC's to their best potential ( such as drivers, RAM Management that works / compatibility with different OS and maybe interface change support ).
A virtual simulator to test out all of our modifications by simulating our respective device just as if we were to cook the ROM ( this could save tons of time rather then just flashing all the time or preventing an accidental bricking of your phone)
And a Universal kitchen for practically any Device ( well TITAN at least for our use ) that works on XP, Vista, MAC, and even Linux.
Im sure with all the developers on this forum and on ppcgeeks we would be able to get this done some time in the future.
Just an Idea....
[email protected]$ said:
What would be great is if we can have a Modifier / virtual simulator / kitchen where we can find ways to modify our ROM's / PPC's to their best potential ( such as drivers, RAM Management that works / compatibility with different OS and maybe interface change support ).
A virtual simulator to test out all of our modifications by simulating our respective device just as if we were to cook the ROM ( this could save tons of time rather then just flashing all the time or preventing an accidental bricking of your phone)
And a Universal kitchen for practically any Device ( well TITAN at least for our use ) that works on XP, Vista, MAC, and even Linux.
Click to expand...
Click to collapse
PPCkitchen buildos is actually the closest you can come currently for easily swapping components around, and there's a universal kitchen here on xda that supports many devices (way more devices than PPCkitchen does).
Don't hold your breath on the hardware emulator
lightbiter said:
hey guy anybody else getting an error unable to make file
when it goes to unpack the ppcgeeksoem rar
Click to expand...
Click to collapse
You'll have to elaborate a little better. If I had to guess, however, I'd say that you might have an older version of winrar installed. As a workaround, you can manually extract and modify the selections to use the extracted dir instead of the .rar.
Now introducing... the HyperCore Athena ROM Kitchen!
First, though, props to anchillus and his HyperCore kitchen. I took it, and made a few small modifications so that it's built for the Athena instead.
Feature Highlight:
Since this is a full-blown ROM kitchen, you can tweak your own ROM however you like. You can do anything that you've seen other people do with their ROMs! All that customizability is at your disposal.
Prepopulated with Windows Mobile 6.1 from the HTC Diamond (5.2.19915).
Prepopulated with applications from the HTC X7501, HTC X7510, and HTC Diamond.
Pictures are not being posted because you already know what Windows Mobile looks like - it's up to you to make it look pretty.
Installation:
Unzip. The "Core" folder goes in as C:\Core. The "HyperCore" folder can go wherever you like; the default HyperCore installer puts it on your desktop.
If you're on SPL 1.2, you'll need to copy an SPL 1.2 OS.nb on top of HyperCore\Build\ROM\OS.nb.
Instructions:
If you want to get your hands dirty right away without reading through the HyperCore instructions, here's the extremely quick version (if you already know how to handle a ROM kitchen):
Make changes in HyperCore\Build. SYS contains the base Windows Mobile 6.1 files, while OEM contains folders that HTC or you provide.
Once you've tweaked SYS and OEM to your heart's content, under HyperCore\Panel\Build, run BuildOS. You'll need to run [1] and [2] to build OS.nb in HyperCore\Build, and then [3] to convert OS.nb to RUU_signed.nbh.
Flash your ROM onto your phone.
...
...
Profit! (j/k)
If you encounter the endless customization loop problem, edit HyperCore\Build\OEM\OEM_Lang_0409\initflashfiles.dat, then find and remove the section for AutoRun.
Known issues/concerns:
The XIP is the XIP from AP 5.0 beta (build 19588.1.1.4, which was from the Sony X1 Xperia ROM). I've tried to generate a matching XIP for the ROM, but it won't boot. Anybody around here know how to create a good XIP?
There seem to be some issues with the Bluetooth OBEX service not being able to start. That's true of this ROM as well. It's able to send files to a PC without a problem, but it can't receive files (although it can copy them).
Even though screen rotation works both in the operating system and in HTC Album, HTC Album's screen rotation has the chance to screw up the operating system's screen rotation. A workaround is to use an application that can restart services (such as the FdcSoft Task Manager) to restart HTC Sensor Service (Athena).
Although the phone skin does work on 128 and 96 dpi, the speed dial application can act flaky and start drawing itself off-screen, which can trigger an error. One workaround is to dial a single number, then rotate the screen, which forces a redraw, after which it functions properly.
The VGA HTC Home plugin could be in slightly better shape. The TabSetting registry entry doesn't seem to work (or at least nobody's responded to me here yet), and the Profile tab shows a keyboard vibration option that, naturally, doesn't work.
The enlarged start menu has some icon overlap on 128 dpi.
The nifty System Status popup on 96 dpi seems to trigger just to the left of the connectivity indicator, while not triggering on the connectivity or signal strength indicators. It does work, just a little strangely on the other dpi settings.
Sym-A now generates the _ character instead of the $ character.
During phone calls, the number keypad is active instead of the alphabetic keyboard.
NOTE:
Much as with Athena Project Kitchen, this ROM kitchen is not to be used for releasing ROMs. It's for personal use only. We really don't need twenty-billion ROMs flooding this forum from everybody who wants that one little tweak.
Exceptions can be made for people who have demonstrated a solid history of producing ROMs. Ask if you feel like you have a strong case for why your ROMs need this kitchen. The current exception list: irus.
Download links:
Megaupload
RapidShare
Other file sharing site suggestions welcome.
Fixes/patches:
Attached to this post. Replace:
HyperCore\Tools\RUU\Athena_RUU.exe with the one from Athena_RUU.zip
Core\ACK\Settings.txt (Updated: July 20, 2008)
I'll be adding additional information to the next few posts over the next several days as time permits (and questions pop up).
P.S. The restriction about personal use isn't about elitism. It's about keeping the forum organized. I just don't want to see every other thread in the forum being a ROM release thread, and there's no reason to make sergiopi's job harder by making him keep track of dozens of minimally different ROMs.
Additional OEMs
NOTE: If you're add OEM packages with modules, you will want to run G'Reloc in your HyperCore\Build directory before you run BuildOS.
HTC EzInput 1.5.31226.0/HTC XT9 1.5.31232.0:
A keyboard designed for use with fingers. There are two large button keyboards (portrait and landscape versions), along with a phone keypad keyboard. The portrait/landscape keyboards swap automatically with the screen orientation. Only works properly in 192 dpi.
Megaupload
HTC LongPressEndKey 1.1.33562.2:
A nifty quick menu program that provides a number of convenient functions. A little less useful on the Athena due to, well, the lack of an end key, but potentially useful regardless. Not tested in other resolutions yet, but likely only works properly in 192 dpi.
Megaupload
Microsoft .NET Compact Framework 3.5.7283.00:
Required for running .NET Compact Framework programs. Meant to replace SYS\NetCF.
Megaupload
WkTask 1.1.7.3c:
A task manager that alters the taskbar to function more like that in traditional Windows, in addition to providing a battery bar and task launcher.
Megaupload
If you would like to change your extended ROM to add packages there for automated installation upon hard reset, you can use the extended ROM editor. You can then convert that with Dutty's NBH tool (available in the kitchen in HyperCore\Tools\Convert) and reflash.
Kitchen Tweaks/Suggestions
Additional OEM Packages:
It's quite possible to find OEM packages out there for quite a bit of software, in order to save yourself time in making your own. If you can't find one, though, there are a number of links on how to assemble your own OEM package - for example, there's a wiki article about making your own OEM package, which also has a bunch of links to existing OEM packages. Just be aware that most of the OEM packages you'll find out there are designed for 96 dpi, and thus may not work on the Athena the way you might expect - the Spb applications are a pretty good example of these, as they come with separate VGA resources.
Package Recommendations:
If you're going to make registry changes, it's usually a good idea to make a custom EM package to contain them. I would recommend using the UUID ffffffff-ffff-ffff-ffff-ffffffffffff, as that will force it to be the last registry file processed (ensuring that your registry entries "win" over those in any other OEM packages).
Package Dependencies:
PACKAGE_Diamond_Album_HTC_ALL can't function properly without PACKAGE_Diamond_HTCGesture, PACKAGE_Diamond_SensorSDK, and X7510_GSensor
PACKAGE_Diamond_VolumeControl depends upon resources in Diamond_LargeTitleBar
RealVGA_DPI_96 depends upon the *_DPI_96 directories in SYS
RealVGA_DPI_128 depends upon the *_DPI_128 directories in SYS
X7510_AudioManager refers to X7510_AudioBooster (menu option)
X7510_TouchFlo depends upon PACKAGE_Diamond_SmartTouch
PROVXML Changes:
If you want to change how your ROM thinks of itself, change HyperCore\Build\OEM\OEMVERSION\mxipupdate_OEMVERSION_100.provxml. ROMVersion is currently set to "Athena_6.1", but feel free to change that to whatever you like.
Registry Changes:
Here's a starter list of potential registry changes.
Code:
[HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders]
"Cache"="\MicroDrive\Internet Explorer\Cache"
"History"="\MicroDrive\Internet Explorer\History"
Move your Pocket IE cache and history to your MicroDrive.
Code:
[HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings]
"MaxConnectionsPerServer"=dword:00000008
Increase the number of simultaneous connections Pocket IE makes to servers to 8.
Code:
[HKLM\Comm\Security\LASSD\AE\{50C13377-C66D-400C-889E-C316FC4AB374}]
"AEFrequencyType"=dword:00000002
Prevent Windows Mobile from screen-locking while plugged in.
Code:
[HKLM\Software\Microsoft\Internet Explorer\Navigation]
"4-Way Nav"=dword:00000000
Have Pocket IE-based widgets scroll by screen, not by link.
Code:
[HKLM\Software\Microsoft\Today\Items\"Wireless"]
"Flags"=dword:00000000
"Options"=dword:00000000
"DLL"="netui.dll"
"Order"=dword:00000000
"Enabled"=dword:00000001
"Type"=dword:00000004
Enable the Today Screen Wireless plugin.
Code:
[HKLM\System\CurrentControlSet\Control\Power]
"WakeupPowerOff"=dword:0000003c
Go back to sleep faster when auto-waking (60 seconds).
Code:
[HKLM\System\GDI\GLYPHCACHE]
"limit"=dword:00008000
Increase the graphical caching. A good size has not yet been determined, although this is the value often recommended for QVGA devices (a VGA device likely needs more).
Code:
[HKLM\System\GDI\SYSFNT]
"CS"=dword:00001000
Increase font caching.
Code:
[HKLM\System\GWE]
"Animate"=dword:00000000
Disable window animation.
Code:
[HKLM\System\GWE\Menu]
"AniType"=dword:00000000
Disable Start Menu animation.
Kitchen History
To be filled in.
Good work!
But...the xip version is after 5.2.thisisxipver and system build is there (Build xxxxx.x.x.x)
You have got a little error
michyprima said:
Good work!
But...the xip version is after 5.2.thisisxipver and system build is there (Build xxxxx.x.x.x)
You have got a little error
Click to expand...
Click to collapse
That's the thing, though - it doesn't matter much to me that it displays the XIP/system version there. Now, if other people care enough to go and change that, it's entirely up to them.
Sogarth said:
That's the thing, though - it doesn't matter much to me that it displays the XIP/system version there. Now, if other people care enough to go and change that, it's entirely up to them.
Click to expand...
Click to collapse
okey...
But...i have my kitchen because previously there arent one...
I can download it for oem packages...
XIP and SYS porting Guide
http://forum.xda-developers.com/showthread.php?t=379598
Here a tutorial and many info... from ababrekar, witha a pictorial guided step by step to download
Sogarth,
Thanks for introducing this kitchen
When I unzipped the download, I had more than 4000 error displayed. Could I ignore them?
Also, you mentioned that for spl1.2, I need to replace the os.nb in the HyperCore\Build\ROM\ directory. But I found that directory to be empty to start with. Is there supposed to be an spl3.5 os.nb there already?
Is this base ROM the same as the one we have been testing in the base wm6.1 thread?
sergiopi said:
http://forum.xda-developers.com/showthread.php?t=379598
Here a tutorial and many info... from ababrekar, witha a pictorial guided step by step to download
Click to expand...
Click to collapse
xipport is old...i use dump rom and build xip by bepe... + ervius pkgtools&buildos
been waiting for a good kitchen for ages. thanks a lot. what build is actually included?
rory
Nice job sogarth, I was looking foward to this all week. i will be giving this a try today
eaglesteve said:
Sogarth,
Thanks for introducing this kitchen
When I unzipped the download, I had more than 4000 error displayed. Could I ignore them?
Also, you mentioned that for spl1.2, I need to replace the os.nb in the HyperCore\Build\ROM\ directory. But I found that directory to be empty to start with. Is there supposed to be an spl3.5 os.nb there already?
Is this base ROM the same as the one we have been testing in the base wm6.1 thread?
Click to expand...
Click to collapse
i am having the same problem is anyone else having this problem
irus said:
i am having the same problem is anyone else having this problem
Click to expand...
Click to collapse
Yep , same here!
michyprima said:
xipport is old...i use dump rom and build xip by bepe... + ervius pkgtools&buildos
Click to expand...
Click to collapse
That's exactly why I haven't linked the first post only but the THREAD address, 24 pages of Q&A, links and files
I have the same problems with sogarth kitchen, the file could be corrupted
Blah. I guess that's what I get for using 7-zip + .zip + BZIP to try and keep everything uber-small. I'll rezip everything and re-upload. *sigh*
works for me if you open in the latest 7zip beta proper, rather than right click and extract here.
Sogarth said:
Blah. I guess that's what I get for using 7-zip + .zip + BZIP to try and keep everything uber-small. I'll rezip everything and re-upload. *sigh*
Click to expand...
Click to collapse
Megaupload kitchen re-uploaded. Rapidshare kitchen in progress.
fards said:
works for me if you open in the latest 7zip beta proper, rather than right click and extract here.
Click to expand...
Click to collapse
I'm pretty sure it works for 7-zip - I think it just doesn't work for non-7-zip .zip supporting programs.
Sogarth said:
I'm pretty sure it works for 7-zip - I think it just doesn't work for non-7-zip .zip supporting programs.
Click to expand...
Click to collapse
well it's about time they started using proper software then
I've been struggling over the past few days trying to get the latest AT&T ROM working in a kitchen. I've tried three different workstations and two Virtual Machines assuming it was an environmental issue.
As a result, I decided to create a fresh new "old style" (PkgToolsBuildOS) kitchen on the assumption that something was wrong with my kitchens.
Noticed the following anomalies in the fresh new kitchen:
1) XIP.BIN / OS.NB.PAYLOAD
Noticed that when performing a Find Date/Rom Version on PAYLOAD or Find Date/ROM Version on XIP_OUT.BIN using XIPPORTEREX 1.2 rev32 , I get the following information:
Date: 06/May/2009
Rom Version: [K] InitDr
I've used the standard process that I always use which yields a working OS.NB.PAYLOAD and even validated it against Aruppenthal & Da_G's sk00ling.
Essentially: PP Unlock, NoCert Patch, PP = 6 MB ... same OEMXIP & MSIXP kernel for now just to try and get it to work.
2) Compiled ROM
If I change the ROM Version & update the Date (as per usual), the ROM compiles fine and boots. However, I am unable to connect to browse the Internet even though the 3G/H data connection appear indicating that a connection is established.
The ROM, OEM, SYS are all 20771 (5.511.502.2) for now just to try and get it to work using my Rogers SIM.
Has anyone else run into similar anomalies before? Cause I'd sure love to know what the heck I'm missing/doing wrong.
* EDIT *
Some of the "paranoid" measures I have done: Rootkit Scan, Full Anti-Virus Scan, Mem Test, Hard Drive Diag, CHKDSK, Restart, typical IT stuff ...
I'm not really sure what could be wrong, but if you need the dump set up for Visual, I had no problems dumping it and uploaded the untouched "Kitchen" to my FTP. Its labeled correctly as the build number 5.11.xxxx. I wish Icould help more, as you have helped me out a bunch.
EDIT: I did dump a ROM recently and got the same Version ID with xipporter as you have mentioned, but thought nothing of it. And I dont remember which it was, so sorry still not very helpful.
The ROM Version "garbage" is odd and IMHO should not be like that - your confirmation that you saw the same thing is very helpful ... at least I'm not losing my mind completely.
I'm trying to keep a PkgToolsBuildOS (5.3) and a Visual Kitchen (9.8) going for folks to use.
I had gone through all of the effort to port 21051 (SYS) and 20771 (OEM) in the hopes of posting it up before the end of the weekend ... then I started running into these unexplained issues and ended up scrubbing the lot.
I'm in the midst of recreating a new Visual Kitchen (9.8) and am discovering additional files in the OEM folder that weren't there before in older versions of the Visual Kitchen - not sure what it means yet; sure hope it doesn't mean having to recreate a kitchen everytime there's an update to the tools.
Cheers,
hilaireg said:
I've been struggling over the past few days trying to get the latest AT&T ROM working in a kitchen. I've tried three different workstations and two Virtual Machines assuming it was an environmental issue.
As a result, I decided to create a fresh new "old style" (PkgToolsBuildOS) kitchen on the assumption that something was wrong with my kitchens.
Noticed the following anomalies in the fresh new kitchen:
1) XIP.BIN / OS.NB.PAYLOAD
Noticed that when performing a Find Date/Rom Version on PAYLOAD or Find Date/ROM Version on XIP_OUT.BIN using XIPPORTEREX 1.2 rev32 , I get the following information:
Date: 06/May/2009
Rom Version: [K] InitDr
I've used the standard process that I always use which yields a working OS.NB.PAYLOAD and even validated it against Aruppenthal & Da_G's sk00ling.
Essentially: PP Unlock, NoCert Patch, PP = 6 MB ... same OEMXIP & MSIXP kernel for now just to try and get it to work.
2) Compiled ROM
If I change the ROM Version & update the Date (as per usual), the ROM compiles fine and boots. However, I am unable to connect to browse the Internet even though the 3G/H data connection appear indicating that a connection is established.
The ROM, OEM, SYS are all 20771 (5.511.502.2) for now just to try and get it to work using my Rogers SIM.
Has anyone else run into similar anomalies before? Cause I'd sure love to know what the heck I'm missing/doing wrong.
* EDIT *
Some of the "paranoid" measures I have done: Rootkit Scan, Full Anti-Virus Scan, Mem Test, Hard Drive Diag, CHKDSK, Restart, typical IT stuff ...
Click to expand...
Click to collapse
Several of the new builds are this way. Its because the date info has been moved. Until someone figures out which part needs hex edited we are stuck with stock dat Version changes fine.
Are you saying that we should *no longer* be changing the ROM Version and ROM Date?
In my case the Date "looked" ok but the ROM Version was bogus.
Which leads to these questions:
Does this also mean that PagePool Unlock, NoCert Patching, PagePool sizing are also in jeopardy of moving? (I know you or others won't have an answer for this one as it's in the hands of the OEM).
Does this mean that PkgToolsBuildOS kitchens and supporting tools are now at end-of-life?
Hate that when I forget to read the memo
UPDATE
Well, after an all-nighter ...
I can confirm that attempting to change the ROM Version and/or ROM Date via XIPPorterEX, PkgToolsBuildOS6.x-5.3, or Visual Kitchen 9.8 will indeed mess up the ROM - at least on the Raphael.
hilaireg said:
Well, after an all-nighter ...
I can confirm that attempting to change the ROM Version and/or ROM Date via XIPPorterEX, PkgToolsBuildOS6.x-5.3, or Visual Kitchen 9.8 will indeed mess up the ROM - at least on the Raphael.
Click to expand...
Click to collapse
So am I correct in assuming that when I change the PP in the 21806 version (as posted by Da_G) it is not really changing the PP. I did wonder why the amount of RAM didnt increase
B4PJS said:
So am I correct in assuming that when I change the PP in the 21806 version (as posted by Da_G) it is not really changing the PP. I did wonder why the amount of RAM didnt increase
Click to expand...
Click to collapse
The PagePool seems ok on my 6.1 builds at the moment but Da_G could best confirm that as he's been on this "circuit" way longer than I.
An observation I made, while I've been working on this, is that the PP size on the AT&T 5.11.502.2 seems to be set 1MB ... at least that's what XIPPorterEX 1.2 rev32 reports when I issue a change to the PagePool to 16MB on a non-reduced ULDR os.nb.payload.
Hmmm, Wonder why when I change my PP to 0 I still only have 197mb Total instead of about 213mb total? Might have to do a test and set it higher to see if my free space decreases
UPDATE: Direct From Da_Grand Pubba ...
Just had a quick chat with Da_G and he confirms that there's been a change in the XIP modules.
At first glance, he noticed that the NK.EXE module has three (3) new resource strings. So in short, if the ROM Version happens to display [K] InitDr (which is [K] InitDriverGlobals) DO NOT attempt to change the Date/ROM Version.
He also had a quick look for Certificate Patching, PagePool Unlock, and PagePool resizing - these appear to be untouched at the moment.
HTH,