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.
Related
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
Okay I have flashed my telus titan many times using the usb method and the flash card method (prefered) now I would like to learn the kitchen method, which I understand I can modify to include the programs I have to load after I do the flash. I get the buildnb and then selecting the programs I like, what I would like to know is if I want to add my tomtom 7 to the build is this possible. plus some other games that I have. What folder to I add these files to? If there is already a discussion about this could you send me a link.
Cheers
I'm not sure how buildnb works, but I'm more familiar with BuildOS from ppckitchen.org and with that, all you do is copy the stuff you find into a folder and BuildOS loads it in as part of it's stuff you can pick from. I would give it a try and see if it's better/worse/indifferent for you. And the guys at ppcgeeks.com are always posting stuff about the kitchen and custom roms. I don't see much here about the kitchen, it's mostly about custom roms.
jc, the kitchen is quite easy to use. But you cannot just dump programs into it and have them available to select from buildnb. The programs that you have will most likely be in the form of a cab. For use in a kitchen the programs need to be in the form of an OEM. There are tools available to OEMize a cab. Just do a search here and you wiull find the tools you need. Then just dump the OEMs into the existing OEM folder inside the kitchen and then when you run the kitchen the programs will be there for you to select. They will install with the ROM, not after it.
You do have other options if you dont want to OEMize your cabs. You can search for Alex's OEMs at ppcgeeks. There are hundreds of premade OEMs for you to select from.
Another alternative is to keep your cabs and just use UC to automatically install them immediately after you install your new rom. This is the preferred method for most of us now as it leads to less problems and allows for programs to be uninstalled at a later date which OEMs will not allow.
Sleuth255 has an excellent tutorial about how to automatically install all your favorite cabs using UC. Search for it and you wont go wrong.
All you need to do is find OEM packages for the programs you want. If you use DCD's kitchen just add them to the OEM folder. If you use PPC Kitchen just add them to the User OEM folder. Then just select them once you run Build OS.
I'm not sure how buildnb works, but I'm more familiar with BuildOS from ppckitchen.org and with that, all you do is copy the stuff you find into a folder and BuildOS loads it in as part of it's stuff you can pick from. I would give it a try and see if it's better/worse/indifferent for you. And the guys at ppcgeeks.com are always posting stuff about the kitchen and custom roms. I don't see much here about the kitchen, it's mostly about custom roms.
Click to expand...
Click to collapse
Hate to break it to you, but this uses BuildOS too, just a different version. Buildnb is just a batch file that g'reloc's and calls BuildOS among other things after BuildOS is run.
I'm trying to learn this stuff too.
Here's some of the stuff that I've found:
OEM Tutorial Thread:
http://forum.xda-developers.com/showthread.php?t=347361
there's more links at the bottom of the 1st post in the thread
Here's the link to packages - say for Kaiser - So I don't know if they can be used on Titan? Anyone knowledgeable please chime in.
http://wiki.xda-developers.com/index.php?pagename=Kaiser_software_recs
??? All the links on Alex's thread seem to be Kaiser based - how much of this is applicable to the Titan and/or other devices?
I agree that ppcgeeks is a good resource too.
DCD's kitchens seems to be fairly easy to do a build. I'm still learning what I want, which versions to include, what everything that's there does, etc...
In theory it seems simple, I'm not finding the learning curve to be all that easy though. A lot of trial and error. But that's part of the challenge, I suppose.
It would be nice if the people with a lot of experience would chime in with tips, links, and comments that would help gather the information into one place for those of us that are learning - maybe I need to go hunt through the wiki's some more, IDK. But sometimes it seems the more threads I read the more confused I get.
My opinion to all of you...and again..this is just MY opinion...take it or leave it...
Build the rom using the kitchen as is with no added personal OEM's. Install all programs/applications/tweaks after flashing either manually, or much easier by UC.
I've converted a few so far, and they haven't turned back. OEM's can be so messy, and can be a HUGE pain in the ass if you need to uninstall/troubleshoot any problems.
My advice would be to read the entire thread on UC, as well as the threads in the Titan Upgrading forum pertaining to UC (I know I've talked about it quite a bit, as well as many others).
Sound good to me. I'm not one who likes to reinvent the wheel if I don't have to, but I am willing to go through a little extra pain to get what I want. If I can get the same results through UC vs. OEM'ing CABs, I'm game. The OEM'ing of CABs so far for me has been a real pain in the arse.
I will do some more reading on UC since I haven't totally gotten the results from that yet that I want. I'm sure my minor problem with the UC cfg file is not unique.
What about adding some of the nueTools into the DCD roms? Reading the text in the included files - some of them can only be rom'd like the ext'd rom utility. Looking that over, I haven't figured out, with any reasonable confidence, how to add this to DCD's roms. I have searched some, but not extensively on this one yet.
This is my latest kitchen. This kitchen is based on Calkulin's kitchen with updates and some modifications done by me. The kitchen is a bit more than a basic setup and should have all the tools you need as you expand your chef skills. It can be used for HTC Diamond, Touch Pro and Touch HD.
This is what I use to create my ROMs found here http://forum.xda-developers.com/showthread.php?t=466438 It is based on
CE version: 5.08.502.1 | OS build: Windows Mobile 6.1 AKU 1.4.6 Build 20771
Basic instructions:
Extract Kitchen base files.
Extract Packages into At0mAng Kitchen - 5.08.502.1 folder
Double click At0mAng's HTC Kitchen.CMD to start
ROM Building:
From main menu
Select Option 1
You will be presented with a device list to build kitchen, select your device.
From there you will be presented with 3 more options, I like to use Option 3, Build a ROM using BuildOS+ Package Tools
Once BuildOS starts click on BuildOS
Leave packages Tweaks, ProFuze Keyboard switcher and Enahanced Video Driver selected (on) so they are include in the ROM you build.
Select other packages that you desire
Once all packages are selected press GO (Green Arrow)
Once BuildOS is complete a window will pop up asking you what Device once again. Select your device.
After that step is complete flash program will begin.
If you do not wish to flash than press cancel and the new ROM can be found in the RUU subfolder.
Advance Features
If you are looking to use the advance features of the kitchen please search XDA to learn how to use them. I only provided the tools in the kitchen so as your cooking skills expand the tools are there for you.
Notes:
All ROMs based on the default setup will have a 16MB pagepool unless you change it before flashing. A utility to change pagepool can be found in the RUU folder.
Make sure you only have one dialer group selected.
Make sure you only have one or none TF3D flavors.
If you are a Windows Live user then cook Windows Live into the ROM. For some reason installing Windows Live from a cab does not play nice with the new ROMs or my builds. Looking into it.
The default keyboard is set for a Touch Pro. I have included a niftly little app called ProFuze created by trinode that allows you to switch keyboard layouts without any regedits or cab installs.
Vista users make sure you have UAC (User Access Control) disabled.
If you would like to learn more about the advanced options of the kitchen then please look around XDA for additional info.
Good luck to all that want to create your own ROMs.
4Shared
Download At0mAng's Kitchen V2 Base Files
Download At0mAng's Kitchen V2 Package Folder
RapidShare
Download At0mAng's Kitchen V2 Base Files
Download At0mAng's Kitchen V2 Package Folder
Thanx!
You are the man!
I will try my Asian version rom using your kitchen.
s2k7 said:
Thanx!
You are the man!
I will try my Asian version rom using your kitchen.
Click to expand...
Click to collapse
No Problem...If you get your Asian version based on my ROM working in Korean can you please post a link for me. Want to put it on my girlfriend's phone since I am working on an Italian version for me
New Version
New Version
why leave everything in the enhancements package checked "off?" Do you mean selected or unselected? Am I unable to pick and choose among them? For instance, I don't want the in-call curtain.
This is pretty awesome though. Can't wait to try it out.
ectopic said:
why leave everything in the enhancements package checked "off?" Do you mean selected or unselected? Am I unable to pick and choose among them? For instance, I don't want the in-call curtain.
This is pretty awesome though. Can't wait to try it out.
Click to expand...
Click to collapse
Ok the only things that should be selected so they are included in the ROM are Tweaks and Video driver.
Updated first post to what should be selected as on for all ROMs.
At0m, thank you for all the hard work. Lately, good work has been under appreciated in these forums. This needs to change!
thespazz said:
At0m, thank you for all the hard work. Lately, good work has been under appreciated in these forums. This needs to change!
Click to expand...
Click to collapse
You are welcome and thanks. Just giving back from what I got out of these forums.
I don't have experience with programming so I just want to try this kitchen, but when I tried. It said "This Software Requires Administrative Priviledge To Run" How to I get my laptop to allow this priviledge.
Thanks
tonsa said:
I don't have experience with programming so I just want to try this kitchen, but when I tried. It said "This Software Requires Administrative Priviledge To Run" How to I get my laptop to allow this priviledge.
Thanks
Click to expand...
Click to collapse
You need to be logged into windows as an admin. If it is a work laptop and you do not have the admin password then you can not run it. If it is your own personal laptop then just log into the admin account and you should be fine or give your account admin rights.
I don't have experience with programming so I just want to try this kitchen, but when I tried. It said "This Software Requires Administrative Priviledge To Run" How to I get my laptop to allow this priviledge.
Thanks
tonsa said:
I don't have experience with programming so I just want to try this kitchen, but when I tried. It said "This Software Requires Administrative Priviledge To Run" How to I get my laptop to allow this priviledge.
Thanks
Click to expand...
Click to collapse
if using vista you need to disable UAC, not just run as administrator
nableezy said:
if using vista you need to disable UAC, not just run as administrator
Click to expand...
Click to collapse
Ah...thanks for the input. I did not even think of that. Will add that to the front page.
When I run, it said missing OS.nb.payload from rom folder.
Thanks
When I run, it said missing OS.nb.payload from rom folder.
Thanks
tonsa said:
When I run, it said missing OS.nb.payload from rom folder.
Thanks
Click to expand...
Click to collapse
Make sure you extacted it correctly. THe OS.nb.payload file is in the ROM folder.
yes I looked at it and it there in the rom folder. I don't know what can be doing it and not able to see in the rom folder.
thanks
tonsa said:
yes I looked at it and it there in the rom folder. I don't know what can be doing it and not able to see in the rom folder.
thanks
Click to expand...
Click to collapse
I just downloaded it and it is running fine. Did you try to do anything else besides build a ROM? Only thing I can suggest is to delete the kitchen folder and extract it again.
I cant figure out how you add packages. I click on Packages to insert in ROM and nothing happens. I need some step-by-step instructions. I have no clue what the execute Xipporter means or anything.
AdamNimrod said:
I cant figure out how you add packages. I click on Packages to insert in ROM and nothing happens. I need some step-by-step instructions. I have no clue what the execute Xipporter means or anything.
Click to expand...
Click to collapse
Add packages by copying whatever package folder to the package folder inside the main kitchen folder.
XIPPorter is an advnace feature. For the advance features please search around XDA to learn what they do and how to use them. There is a good thread in Deve and Hacking. It is not needed right now if you are just cooking. If you are looking to port different builds from different devices that's when it can come in handy.
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,
Hi all; I am new (here that is) but am fully capable microsoft certified & mvp coder.
Who is or want's to be or can help working on magldr compatible wp7 Kitchen and initial live-activated dwi rom?
1st goal here to make a kitchen then for hello_world just rebuild leo70 with live activated. Maybe get together here and setup proper dedicated irc. This may not be normal way to go about but I am not interested in social netiquette distractions. Just want to work on this and get it done. I have been using dumps (both my own and this: http://forum.xda-developers.com/showthread.php?t=915978 ) along with jtag, and everything at my disposal.
I am doing this now with progress already made and have been working on this since prior to leo70 public release.
if interested or have news or info please post here or pm me- thanks.
G-ThGraf said:
Could we make a WP7 ROM with Chevronwp7 and all tweaks i cooked in?
Click to expand...
Click to collapse
I am hoping to and trying to and will make a kitchen and then this so soon: YES!
leo70 said:
Anyone made any moves on .rgu to .provxml to enable service mode on leo70?
REGEDIT4
[HKEY_LOCAL_MACHINE\System\BootLauncher]
"Default"="ServiceApp.exe"
or:
REGEDIT4
[HKEY_LOCAL_MACHINE\Drivers\USB\FunctionDrivers\TFTP]
"DeviceName"="USBFNS3:"
"USB_MaxPower"=dword:32
"bcdDevice"=dword:00000000
"Product"="Generic Serial"
"idProduct"=dword:00000629
"Manufacturer"="Generic Manufacturer"
"idVendor"=dword:0000045e
"IClass"="{CC5195AC-BA49-48a0-BE17-DF6D1B0173DD}"
"Flags"=dword:00000002
"Prefix"="FTP"
"Dll"="tftp.dll"
Anyone use trivial ftp for FUU? anyone called these DLLs or used/moded these keys?
also: per Da_G partition layout and comments for wp7 hard spl: for FFU/RUU: is it serial or usb/kitl/ethernet?
I think injecting a certificate into leo70 and rebuilding dump up will then allow an ffu to be flashed; debugging this then leads to a lot; hspl, kitchen, new roms.
Click to expand...
Click to collapse
Where is all the action/info !?
I wish you all the luck to make this a wonderful experience. Hope people with relevant knowledge and skills join you for this cause.
first there need to be some tools to be made , like Reloc , rebuild imgfs , maybe a platformbuilder like bepe did.
after that you could make a kitchen.
Da_G have posted some interesting information in WP7 Development & Hacking section
http://forum.xda-developers.com/showthread.php?t=649914
maybe this would also help to understand the structure of the (our DFT) rom.
Sounds good guys. Potentially integration of the android set up could be good bypassing the need to copy partitions across etc.
Wow ... good luck my friend
-------------------------------------
Sent via the XDA apptalk leo android
The imgfs rebuild with all modify is possible with tools here http://forum.xda-developers.com/showthread.php?t=685272
But a this time i don't find way to rebuild flash.store.bin (part04.bin = os.nb) content bin's:
LOGO
BLDR
NK
SLDR1
SLDR2
IMGFS
USER
...
Maybe the DFT wait to give the tool for community ??
;p
Good luck seems an excellent idea
netdrg said:
The imgfs rebuild with all modify is possible with tools here http://forum.xda-developers.com/showthread.php?t=685272
But a this time i don't find way to rebuild flash.store.bin (part04.bin = os.nb) content bin's:
LOGO
BLDR
NK
SLDR1
SLDR2
IMGFS
USER
...
Maybe the DFT wait to give the tool for community ??
;p
Click to expand...
Click to collapse
HazzBazz said:
Sounds good guys. Potentially integration of the android set up could be good bypassing the need to copy partitions across etc.
Click to expand...
Click to collapse
sandman01 said:
Da_G have posted some interesting information in WP7 Development & Hacking section
http://forum.xda-developers.com/showthread.php?t=649914
maybe this would also help to understand the structure of the (our DFT) rom.
Click to expand...
Click to collapse
ceesheim said:
first there need to be some tools to be made , like Reloc , rebuild imgfs , maybe a platformbuilder like bepe did.
after that you could make a kitchen.
Click to expand...
Click to collapse
Cool.
we can at least discuss it all here maybe: put all relevant info together.
I agree with u ceesheim, with tools required etc.
What about 7/CE platform builder though, modify, plus existing tools for imgfs etc? I was thinking also: for now anyway: just disassembling dwi.exe and figuring out all of the other partxx of this build which gets around non-wp7-spl. its a great hack and bears with it some interesting methods which may lead to other things.
I am really just exploring all options for now; any ideas, thoughts, discoveries? To be honest I am only reverse enginerring it all and have not yet tried to rebuild flash.store.bin (part04.bin = os.nb). Was going to try a few os.nb in there and just see response of magldr etc. Been lazy last few days lol.
But point is seems FUU/RUU and then Cotulla,DFT,Bepe' DWI give us two different paths to explore here!
What are exact known problems & current states on that: trying to do dump to (re)-build+flash?
I think that is where I will work - figure out other partxx.bin and magldr and disassemble dwi.exe to make flasher.
Thoughts?
ceesheim said:
this is used to dump it :
http://forum.xda-developers.com/showthread.php?t=884239
I think it was part 4 you had to rename to .nb and then open in this rom tool.
Click to expand...
Click to collapse
netdrg said:
i use the tools here http://forum.xda-developers.com/showthread.php?t=685272
For make this dump
Click to expand...
Click to collapse
ceesheim said:
only different is that the tools from da_g are command line .
the link I posted is more noob prove
I just tested it , rename part4.bin to part4.nb
then open romtools and click open ,go to the location where you stored part4.nb and click it and hit the button open
Click to expand...
Click to collapse
Yep, thanks guys.
I use them all depending on what I am doing. Da_G great: use all these tools 4 imgfs, xip, uldr, xph, etc and yeah - can get same for part04.nb to rie. What been discovered/worked out for other partxx.bin of 'myname' ? emul' wp7 spl etc opened, explored? Anyone know overall kitchen progress thus far? Hope wp7 kitchen ppl can get together more so and get this done!
leo70 said:
Ok.........
Anyone looked at rgu for serviceapp.exe or got anything on this? calls to DLL for Trivial FTP for FUU? Also: questions if any wouldnt mind:
anyway to tweak dwi.exe just like daf.exe and use switches like |ro| and other switches and set part layout size etc? originally thought could force magldr to convert-extract by putting other partxx.bins on part(0) user then do userdata dump to .img but layout! and prob it just dump in original .bin anyway? not quite sure how dwi places converts- containers, fs, etc?
What IS known about magldr, partxx.bin(s), dwi.exe?
Yeah, im being lazy, maybe too hopeful here on these ones, but worth asking. I will fully disassemble dwi.exe later on .
If problem with rebuild .nb/.nbh perhaps use another kitchen like zero or visual osbuilder with wm6 and just rename .nb to part04.bin to even see if it will load at all; debug this and watch this strap up; I might try this with stock os.nb made to fit to size. CRC?
it may fail totally but I want to see why and where/when/by what. ie: interaction with wp7 hd2 spl emulacrum and other parts+magldr. Will cotl' spl etc get wm6; should 'understand' wm6 os.nb?
Might lead to exploration of other partxx.bin from within wm6 or mtty. another thing is mtty. Mtty brings other ideas into play; if we know Cotulla and DFT layouts etc and truly understand magldr, partxx.bin, dwi.exe, and emulacrum spl, then we can go another way: that is all I am really saying here.
Especially considering how it is built and lack of tools/info on this ***particular*** wp7 build.
Click to expand...
Click to collapse
Ok.........
Anyone looked at rgu for serviceapp.exe or got anything on this? calls to DLL for Trivial FTP for FUU? Also: questions if any wouldnt mind:
anyway to tweak dwi.exe just like daf.exe and use switches like |ro| and other switches and set part layout size etc? originally thought could force magldr to convert-extract by putting other partxx.bins on part(0) user then do userdata dump to .img but layout! and prob it just dump in original .bin anyway? not quite sure how dwi places converts- containers, fs, etc?
Yeah, im being lazy, maybe too hopeful here on these (ffu/ruu) ones etc, but worth asking. These are what I will figure out/we need to. Also noted "wph" string in daf.exe for droid. interesting. so yes, bypass option seems real.
edit: going back to what I said above, replacing part04.bin COMPLETELY with equivalent size os.nb (rename back to part04.bin) and flashing with dwi.exe? there is a plethora of things that could be attempted this way. crc? size? errors? not sure, but there is that hd3/hd7 experimental leaked "hd2 wp7" rom that wouldn't flash to hd2 under normal spl. and a lot of other things here to do; I am just interested in this as it bypasses all normal known spl mechanisms completely! You can flash anything you want without checks etc. And then explore interaction with Cotulla' spl (wp7hd2LEO1000) and other partxx.bin etc. Thoughts?
As far as orthodox methodology goes, so, bepe_cotulla_dft made a complete new platform builder and bsp? thoughts on where to start without this?
Please note I am a windows (nt) kernel coder and getting my head around phone7, ie bsp/oal=hal (!) so please bear with me! Who is working on Transaction Safe exFAT? any progress towards cracking? what is Encryption used in TexFAT? Along with kernel/drivers (nt x86/x64) also have cryptography experience. Sorry for all the questions! umm, in summary:
I am also assuming other partxx.bin(s) of DFT release are SPL, OEM, OEM RO, etc.
***Anyone got up KITL and/or can debug this leo70 release? (please answer with instructions etc!).***
edit: with above factors being case, I will fully disassemble and reverse magldr, partxx.bin, cotulla wp7 hd2 spl, os.nb, dwi.exe later on . edit: am doing now. whilst reading architecture for windows 7 phone! Kitchen will be done, but ability to just flash and part layout initially required imho! I am going to take control of magldr, cotulla wp7 spl, dwi.exe first: doing this now .
Sorry to spread over few posts!
Ultimately thus, concluding, I think key here is to reverse engineer all (cotulla' wp7-hd2-spl emulacrum, magldr, os.nb, all other partxx.bins, dwi.exe) then create new open set of each these and new flasher: anyone explored this, disagree, agree?
This is what I am doing now .
Got IP address & can see what is being done.
i like your work
keep up what u doing and i hope to get it done so we can finally use wp7 unlocked and activated
thank you...
@Leo70
I'm a coocker (for windows mobile 6.X) so if you need some help i think i could help you. Just PM me if you need
Why don't you ask Cotulla? Reverse Engineering will be much more longer?
I think they are working on a new MGLDR so why do your own thing on your side?
Can you put a file in the installation process where we can put our Live ID Code?
If every one have the same market ID that will possibly be a problem in the future?
I'm not trying to teach you anything don't really now about dev stuff just wanted to share my thought and opinion.
looking forward to this kitchen....
ok, after 3 days of attempting to download RUU_Schubert_HTC_Europe_1.60.401.01_Radio_5.52.09.16_22.33a.50.10_Signed rom i had finally been successful so i thought i should try out swapping stuff to determine what each part**.bin represents.. started off with the basic os.nb swapping and tried flashing magldr to see the changes..
i hate to be the bearer of bad news but it seems partition size & info are hardcoded into DWI.exe so the file size change doesnt allow for a successful flashing..
so lets hope it will be more flexible when magldr 1.13 is released (which is going to be released "soon" as in no specific eta) otherwise this kitchen might just serve the purpose for building nb's/nbh's for other devices..
But im sure this issue is only present in magldr 1.12 dwi.exe as the wp7 rom wasnt released officially in xda, however only time will tell
Only time will tell, fingers crossed
this project sounds great. a already tweaked rom would be awesome and an pre activated rom even better.
keep up the work. maybe you should contact cotulla and ask him rather than reverse engineer everything. maybe he will help you and save you a lot of work.