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,
Related
I just put together the following pieces
OS 1.72.00WWE
Radio 1.17.00
ExtROM 1.72.902
"CountryCode" = TMOBILE
All configured for T-Mobile NL
Plz. Post any comments
(Plz. note this thread replaces http://forum.xda-developers.com/viewtopic.php?t=11781 )
8-11-2004 20:57 GMT: New version V2 uploaded.
I added a small archive containing the changed ExtROM files to solve the earlier reported errors (not updating ExtROM version and not making IIWPO un-installable).
Comment on IIWPO and making it un-installable: After having customized & installed IIWPO, you will have to do one of the following to make it un-installable if youre using the 1.72.902 ExtROM:
a. Another hard-reset
b. Running Version_172_902.cab from the ExtROM
NOTE: This thread is being replaced by
http://forum.xda-developers.com/viewtopic.php?p=68652#68652
Thank You!!!!!!!!!!!!
I am d/l'ing right now and will be installing shortly...
One request... You might want to include the cab for setting up IIWPO in case someone is installing it into the phone.
edsub Thanks.
Question tho. Can I use this for T-Mobile USA and does it fix the MMS problem ?
asking because the version says NL, isnt that the Netherlands country code ?
Thanks again
Well from first look everything seemed ok.
THese are a few of the things I have noticed since loading.
1. The ext rom version # doesn't show up in the info
2. If you use the IIWPO then it still shows in the remove list
3. The new apps from the 187 version will not install no matter what you do. (I have tried adding the ver # in the Reg, both 902, and 187 (not at same time)) Niether worked.
These are the few things that I have found since loading. If I find any more I will loet you know. Other than these I think you havea winner here!
I was wondering about the streaming MMS, the new bluetooth stack, and some of the other new versions of software that came in the 181,187 packages, and why you didn't include or update to them? Was there some incompatibality issue?
Thanks and great job!
Re: Home-cooked 1.72.902 upgrade package (1.72.00/1.17.00) T
edsub said:
I just put together the following pieces
OS 1.72.00WWE
Radio 1.17.00
ExtROM 1.72.902
"CountryCode" = TMOBILE
All configured for T-Mobile NL
Plz. Post any comments
(Plz. note this thread replaces http://forum.xda-developers.com/viewtopic.php?t=11781 )
Click to expand...
Click to collapse
Is SRS included?
SRS is not included due to the fact that I don't see any use for it personally. Since it is an ExtROM installer, you could add it yourself.
The NL is only there because some sdetting are more or less specific to the Netherlands. I had feedback on my earlier 1.72.901 package that it worked for other countries (incl USA) as well. Be prepared that the date format will be dutch by default (easy to change via settings though).
Also MMS is suposed to be working (but I have not tried it due to lack of interest in MMS)
The ExtRom# is not showing because some bug in the Version_172_902.cab. Working on that now.
IIWPO not showing in the remove programs list is a bit more difficult than it seems if you install for the first time. Normally you would boot up the device with new rom. IIWPO is NOT installed at this point. Once you have customised & installed IIWPO, you will have to do ANOTHER hard-reset (ie run the ExtRom contents again) to disable the uninstall. You could force this by hand first time to re-run Version_172_902.cab after installing the customised IIWPO. BUT as this cab is not OK, it wont work anyway. Working on that now.
I did not find the time to look into the new O2 apps. If someone finds a solutiuon here, I am more than happy to includew it in a new version.
For the streaming MMS, the new bluetooth stack, and some of the other new versions of software that came in the 181,187 the basic reason is lack of time. I dont know what 'extra' new there is on bluetooth in the O2 builds? OS Rom 1.72 allready has an updated BT stack that fixes most open issues. I have no experience (& interest) in MMS / streaming MMS . . .
I suppose the issue with TomTom locking up without GPS enabled is not solved with this rom ?
I know: wishful thinking..........
@Pleun: Nope. I WISH I would have solved that one!!! FYI: I tested he new TomTom GPS 3.07. It doesnt solve any locking issue and next to that makes my Headset react very slow. Also the 'Bluetooth GPS' option that is supposed to solve the locking has gone, at least with my installation. Not advisable. I reverted back to TomTom GPS 3.03.
@all: I solved the issue of not setting the Ext Rom version and making IIWPO non-uninstallable. New version V2 will be up in 10mins (incl. incremental fix for all that downloaded the version from yesterday).
New V2 is up now. See first post in thread.
Plz keep posting comments to make this upgade better
edsub said:
New V2 is up now. See first post in thread.
Plz keep posting comments to make this upgade better
Click to expand...
Click to collapse
I feel like my MDA2 is a little bit slower to respond not sure why! I added PocketMVP, Belkin Bluetooth GPS, Resco Explorer 2003 V5.0 and .NET Compact Framework 1.0 SP2 for Pocket PC 2003.
I am having problem with Belkin BT GPS; I got it to bond, detect the COM port (COM5) and baud rate(4800) to use but my MDA2 hangs up and had to soft reset. Any idea why?
I will try to install one by one and see what's causing it and report here.
edsub thanx for me it works great its a great improvement!
machine seems faster and no more lock-ups.
Keep up the good work (ill be following you)
p.s only one thing my battery seems to give me no more than 4 hours of on-time
4 hours is very different from my (and others!) experience. The 1.72 rom should even improve battery life.
My battery lasts for about 1,5 days (not measured but recalled from my memory) with approx 1-1.5 hours on the phone and bluetooth permanently switched on . . .
were can I download this rom from?
from the first msg in this thread : RUU172902WWE_eDsuBsofT V2.exe
Hi me again, dont want to sound stupid but I've tried both Opera and Explorer and cannot find any executable file in the first post. Normally it appear in some sort of info box but none to be seen on this thread and the link to the previous one!?!?! Is this something to do with XP SP2?
Anonymous said:
Hi me again, dont want to sound stupid but I've tried both Opera and Explorer and cannot find any executable file in the first post. Normally it appear in some sort of info box but none to be seen on this thread and the link to the previous one!?!?! Is this something to do with XP SP2?
Click to expand...
Click to collapse
You cannot download it as a guest! If you are a member of this forum you have to log-in before you can see the file you want to download. That's what I encountered before so just try logging in first.
Good luck!
THank you very much superperry. Should have registered before but was always too lazy.
I have put together rom upgrade 1.72.903
This thread can be closed. See http://forum.xda-developers.com/viewtopic.php?p=68652#68652 for the new one
Edit: The new upgrade files are now available (see refered post)
An error need help please
I downloaded the files then followed the instruction below but now I get error
the flashing process
first the devicedata is obtained from the device, with HimaGetDeviceData.exe, this gets the operatorname, and language/country code from the extended rom, sector 2 of the BDK.
Then a tool 'HimaClearJumpCode' is executed, which erases the jump at the start of the kernel. causing the bootloader to start at next reboot.
the upgrade tool then connects to the bootloader of the xda, via serial over usb. ( port \\.\WCEUSBSH001 )
warning do not just run the 'HimaClearJumpCode' program, it will erase part of your OS rom, after which you will have to repair your device by running an entire upgrade again.
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.
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.
Just flashed my latest ROM to my device as per usual using PkgToolsBuildOS-5.3.
When the device starts, the version information displays:
1.12.25.19
52.60.25.33U
5.08.E12e
Yet, if I flash the same ROM using my Visual Kitchen, the version information displays:
1.12.25.19
52.60.25.33U
5.08.00.00
I've gone through both kitchens file-by-file, folder-by-folder, using a comparison tool and they match. Additionally, everything seems to operate as expected ... just the boot screen information is odd.
Any insight as to the meaning of the E12e would be greatly appreciated.
Have you used ROM tools to check version of xip/payload? Do they both match as well? I'm guessing that you didn't make the change by accident in the older kitchen. Its pretty easy to change in old kitchen compared to opening XIPPORTER and viewing/changing in new one. Have you tried a recoook in the old kitchen and got the same result? Try changing the value and see if it sticks.
So, are you also making the switch to new kitchen? or just doing some testing?
if u r using the new visual kitchen, i believe u must check S000 in nk.exe modules folder. Or u can check that later on finished *.nbh. Find for the unicode E12e using hex editor (etc) & u will find it near the ROM date. I'm sorry if this not helping but i tried
Appreciate the quick responses.
I'm in the process of preparing two kitchens, one using PkgToolsBuildOS 5.3 (old style) and one using Visual Kitchen 9.x (new style). Both kitchens contain the exact same OEM/SYS and PACKAGES/EXT structure.
The XIP.BIN has been CERT & PP patched, ULDR reduced, and the PP set to 16MB.
In case you're wondering why identical kitchens in both formats; i'm trying to get them ready to post up for use by less seasoned chefs for comparison purposes. Was just about to post-up when I noticed the oddity and figured I'd check before.
Both ROM's work, just the version on the boot screen (as above) on the old style version ROM.
Weirdest thing.
* UPDATE *
Well ... after 2 hours of fiddling with the kitchen, I rebuilt the os.nb.payload since that's the only thing that is different between the kitchens - problem solved.
First things first! As the topic states, this is a *TEST ROM*
DO NOT expect this ROM to be usable for every day use
DO NOT expect this ROM to be well tweaked for performance
DO NOT expect this ROM to ... you get the idea, i hope!
This is the first Test ROM for the Image Update service - this ROM has a 1024KB free space buffer for NK partition, 20MB free space for OS partition. This should be enough to facilitate several ImageUpdates for testing. (It's not intended to have enough space for you to add all your chosen apps for every day use - this is just for TESTING!)
It's based on WM 6.5 21812. This ROM is unique in that both the NK and OS partitions are completely uncompressed, rather than using either XPR or LZX - so i'm testing that too. Please report on overall system performance of the BUILT IN applications (not cabs or packages you install) - i'm wondering if Uncompressed is viable at all vs. XPR and LZX. So far i'm thinking no (60MB LZX -> 80MB XPR -> 150MB Uncompressed) - but testing is warranted!
The Image Update packages for this ROM are now in post 2!
Here's the download link!
Again, this is BAREBONES, the ONLY thing it has is drivers and comm manager, this is done on purpose, so that we can have as few variables as possible while testing deployment
http://rapidshare.com/files/244900505/ImageUpdate-ready-ROM-Raphael.rar
Some notes:
The ROM has an OS pagepool size of 26MB
The ROM has a ULDR pagepool size of 4MB (up from 1mb)
All compression is disabled entirely (not XPR or LZX, but Uncompressed - both on NK and OS partition, also compression is disabled on individual modules and files)
Dr. Watson (Error reporting) buffer reduced from 300K to 0K
Update Packages
QuickGPS
EzInput+eT9
Camera - This will install the Camera, Dshow, Mhub, and SensorSDK packages (Camera is dependant on the others)
Here's the test case scenario - create a directory named "Release" in your filesystem, at the root \ folder (so \Release)
Copy the cab.pks to your device, or sd card, and run it as you would a cab
Note any errors or anything that might occur before the process succeeds or fails
If the process fails - please attach the logs found in \ and \Release to a post, so we can analyze it further
If it succeeds, time to hard reset your device!
Check and see if the package remains after hard resetting.
If it does - We have a winner
A live-updating rom with no need to reflash the device after each upgrade? I love it!
Keep up the good work!
Interesting concept.
this is awesome! cant wait to cook one for kaiser(hint, hint) thanks for all your work, this is going to change EVERYTHING.
Image Update System
I have been following the WM Image Update System thread and the idea sounds very doable. How can we help?... David.
I can Hard reset my phone every day, so if you in need of any volunteers Im here .
I have been following your kitchens for a while, and it's time to return the favor.
Thanks so much for your hard work Da_G!!
-------
HTC Fuze - WM6.5 21812
Da_G...Sir, you are a saint and a scholar...when this is finished it will be the coolest thing since velcro...
I would love to help just let me know how...would be happy to test..report...etc.
Dreaming of the day...no more hard reset
Da_G,
Thanks for your hard work.
I'll been dreaming of the day when I don't have to reflash my ROM or hard reset just to update the software.
I'll beta test and give you report.
D/Ling now, will report after work this evening. :excited:
i am really enjoying the speed. its unreal. every thing else seems normal. i am still loading up my apps right now. i'll post up some more when i get home.
the speed and respon se is secon d to none . i am very much plea des with the performance .
i know you said its barebo nes....so. i will view the lack of came ra e xe and .net. fram ework as by design . let me know if there is anyt hing spe cific you want me to test .
rzanology said:
the speed and respon se is secon d to none . i am very much plea des with the performance .
i know you said its barebo nes....so. i will view the lack of came ra e xe and .net. fram ework as by design . let me know if there is anyt hing spe cific you want me to test .
Click to expand...
Click to collapse
I'm going to need you to test your awesome space bar, it seems to be more than working well... =P
LOL, didn't overwrite CompIME.dll in this release (again for compatibility reasons) so that's why the jacked up spacebar..
But hey, it's a test
Hoping to have packages for you soon
Everything is working smoothly, no issues yet. I read your other post on the image update and want to know how far into user customizablity we can go without messing up the update process, ie. regedits, packages, etc.. Or if its a secure core that we can't really mess up.
Oh, yeah, its supper snappy and extremely responsive. And running at 26% Memory isn't bad either.
Is it safe to assume any updates needed to be deployed, such as over writing the CompIME.dll will be done thru the this new Updating system, correct?
Thanks for your hard work Da_G!!!
So, am I correct that any chefs who want to incorporate the working updating system into their roms will have to cook unprotected? This could get really interesting, LoL.
Thanks for the awesome work!
@Farmer Ted:
Yes, to support Image Update, ROM's will need to be fully "unprotected" - protection is really just damage to the ROM structure that still allows the phone to work
@NFRCER:
Yep, that will be one of the first test packages probably
@danthman2000:
The only thing you need to be concerned about in doing mods is that any files you replace or registry settings you change that might be in a future update, the update will not apply them, unless its specifically set to override your settings by using an mxipupdate_*.provxml - but the creator of the package should be aware of this before hand - so if it needs to override any of your settings it should be set to.
By the way, I plan to have the first test .cab.pkg up by tomorrow, so if you're sitting there with the test rom flashed, might wanna go back to a working one for now
Da_G said:
@Farmer Ted:
Yes, to support Image Update, ROM's will need to be fully "unprotected" - protection is really just damage to the ROM structure that still allows the phone to work
@NFRCER:
Yep, that will be one of the first test packages probably
@danthman2000:
The only thing you need to be concerned about in doing mods is that any files you replace or registry settings you change that might be in a future update, the update will not apply them, unless its specifically set to override your settings by using an mxipupdate_*.provxml - but the creator of the package should be aware of this before hand - so if it needs to override any of your settings it should be set to.
By the way, I plan to have the first test .cab.pkg up by tomorrow, so if you're sitting there with the test rom flashed, might wanna go back to a working one for now
Click to expand...
Click to collapse
A working one? This one is working beatifully lol .
Im curious, I checked the system tab, and I didnt see the Windows Update Icon...
How will we check for the update then? Just wondering, thats all.
My apologies if im asking too many questions
Great news Da_G. I'll test it once you post the update tomorrow. How do the updates get delivered?
Is the .cab.pkg a small file which contains the server information so the phone can go out and retreive it? Or is the .cab.pkg the whole kitten caboodle?