The material provided in the unofficial theme. In the case of a failed flash unit, and the topic of the site is not liable! All actions are at your own risk.
I present you the firmware WM 6.5.Standard Build 23 017
Just a flashing 3 languages (0407 (German), 0409 (English), 0419 (Russian)), the default English. And 3 input language.
Screen theme (Sliding Panel & Sliding Panel Media) converted from Rose Sliding Panel's, which made it possible to use HTC Weather.
After the firmware necessary to reboot the device!
Programs: Celetask, CHome configurator, Clock on Top, WM5torage, Registry edit.
Links:
http://www.mediafire.com/?hnd324uanwwz0id
https://rapidshare.com/files/3185754262/6.5.BIN
Calls, SMS sending, SMS takes, SMS as chat, Bluetooth works, in general, everything seems to be working pretty well!
Thanks to all who helped in creating this firmware!
downloading - will give you feedback asap
I have checked on the package and here are the comments:
The backlight/display driver is not acting according to the settings in the control panel. The display does not get off. The light gets off - but not the LCD. You can see that when you put the display in bright light. When making my kitchen for WM6 I have tried out several different drivers all having one or the other problem and finally decided for the one present there. Please re-check your choice in the light of above problem which creates a big battery drain unfortunately.
The German language is only fractional available. I think that the packages are missing some .provxml files or that these are not read correctly. You can cross-check needed actions for multi-language in my beginners guide for cooking. Especially tracking down the correct execution of .provxml is tricky. There are some threads at XDA dealing with this. I found finally that using the rapiconfig tool on the connected PC sending the files for execution is giving a fast and reliable method for debugging. Search for "provxml" and "rapiconfig".
For my kitchen I had added at the end of each .provxml a registry entry to write to HKLM\Platform with the name of the .provxml as an entry. This way you can check if the file was executed in the first place and then further investigate which was not.
Finally I have seen that the WM65 allows to have skinned menus which complement the sliding panels appearance. Would be good to see that in the WM6.5 ROM as well.
Good luck with your further cooking!
Oh one last thing: You should change your topic title to include "WM 6.5". Not all know that WINCE 5.2.23017 is one internal version of the WM6.5. I think that WM6.x translates to WINCE 5.2.y before that was WM5 with WINCE 5.1.z.
tobbbie thanks for the posts!In other rom, i want to do all languages good!
Upd.04.09.11
Hmmm... I don't know what with backlight driver!!!I i don't change him!
Nex update will be only with 2 languages (en-ger and eng-rus) because, i don't know how edit mxip_lang.vol!!!
Have you done anything lately to the ROMs? I finished my Typhoon and Tornado porting to OS Builder, so Hurricane is on the list now to have these old candy-bar phones complete on OSB.
When dumping the ROM with OSB, I noticed that you had used the "merge packages" option when assembling it. This makes it harder to get started, though not impossible as I have the XIP to build my own 6.5 (which I used from the Captain for the Tornado).
Where did you get the base from?
Which kitchen tools have you used?
Hi tobbbie!
Ok, i send you archive later.
but there is a problem, display driver(backlight) don't work correctly(i trying 5 or 6 backlight.dll) and if driver saving power correctly, when you receive incoming call, display don't turn on =(
I think best choose for hurricane is 6.1 =)
It is strange with the backlight. Usually the OEM parts are those that do NOT change in the porting process and so their behavior should also not when the SYS changes.
Problem with the Hurricane is that many OEM modules do not have a relocation section and so can not be properly relocated by some tools. In the batch kitchen I used, the wmreloc.exe could magically do the job nevertheless, probably by making clever general assumptions on the structure of the modules.
When porting Aleut's WM65 for Typhoon to OS Builder I have identified the modules without relocation section (wmreloc writes a special file to the modules folder for those) and "nailed" them to their current location by adding them to the OSB list of "do not relocate" modules.
To be sure that you start with a working set of modules, it is mandatory to start with a dump of such a working device and not a fresh directory setup - where you would rely on the relocation to properly work for ALL modules.
For Typhoon there were just 5 modules without relocation section because there existed a leaked WM5 "dogfood build" for that device. This had all modules including their relocation section. So just the non-Typhoon (Feeler and Amadeus) specific things (keyboard I remember) needed that special treatment.
For the Hurricane I had counted many more such modules and I am not sure if I will ever get a running OSB setup for this. Last time I tried I could not even get my working WM6 setup rebuilt, so this project may find an early ending.
Good news: I got my WM6 build running and re-built with OS Builder. Took some time to discover that the empty boot.rgu from OEMXipKernel package has left out the Launch20=service.exe from the resulting registry, which made the boot stop at that point.
So nailing the OEMDrivers does work here as well - there is hope for more to come here as well
Tobbbie, it's fantastic!!!
I use your kitchen to create imgfs.bin, then i use imgfs.bin with program nbwork to create os.nb(with uldr.bin xip.bin imgfs.bin) and then use you program xipbin =)
To port wm standard roms, i also tryed 28004, and once it's work, but there is no different =)
P.S. links add some minutes later, now uploading to mediafire.
Thanks for your work!
link: http://www.mediafire.com/?qu1x574f8u437g0,lb4ha9rm53n9gpu
And i also rying to poted wm pprofessional on hurricane,it start, but work with some lags, and need to rewrite some oem drivers =)
Why do you need extra tools outside my Hurricane kitchen set? If you put the WM6.5 XIP and Partition framework in the Source folder with the right names then the batch should deliver a ready-made .bin at the and as well.
The easiest way to get back to the one-step batch would be to pick one of your two-step created .nb files, rename it to 82040000-OS.nb and put it to the SOURCE folder.
Batch processing will cut out the pieces and supply the compression for imgfs later - no more two-step.
Last step of the kitchen is basically to joint the new created imgfs with the already ported XIP and ULDR (if present) to a new .nb and then put it to transfer format of the BIN file - transparent blocks with some kB size (not sure if it is64k) and a checksum so that transfer errors can be detected.
Anyway the important part is the creation of the imgfs and especially the correct relocation of modules, something special with the Hurricane and its many modules without reloc section.
You up'ed 2 files, one named "part1.." is there a part 2 also or is this the create_wm6_5?
I guess I will just use the SYS I have for WM61 (from Rose) and WM65 (from Captain) in my Tornado OS Builder kitchen for porting inside OS Builder. This is easier than porting from Batch to OS Builder.
I see no advantage of WM65 over WM61, but all done for the WM61 can be transferred 100% to WM65, so no big deal here. The added functions on WM65 are not worth it:
some memory and CPU hogging browser ad-on
and "widgets" you cannot use on smartphone anyway
and a 1MB bigger SYS with otherwise identical packages
make not up for the option to be able to skin your menus, they just get bigger and making that finger friendly on smartphone is a joke
Sliding panels are in WM61 already (for those who like it) but I have my private homescreen that does all I want on one page and it includes ToDos which the Sliding panels does not.
---------- Post added at 05:10 PM ---------- Previous post was at 05:08 PM ----------
sniper304 said:
And i also rying to poted wm pprofessional on hurricane,it start, but work with some lags, and need to rewrite some oem drivers =)
Click to expand...
Click to collapse
Why professional - you have touchscreen on Hurricane? Just the 96DPI is nice for more screen estate (smaller top/bottom bars) - but I don't care, really.
---------- Post added at 05:12 PM ---------- Previous post was at 05:10 PM ----------
BTW: WM6 Kitchen runs full gear and all options - time to port to WM61 and WM65
in part 1 your kitchen with sys 6.5
in create 6.5 nbwork and rom files(uldr.bin xip bin)
I don't like imgfstonb tool =)
Some times i get bad roms, with bugs, but when i used nbwork, all roms work good.
tobbbie said:
I see no advantage of WM65 over WM61, but all done for the WM61 can be transferred 100% to WM65, so no big deal here. The added functions on WM65 are not worth it:
some memory and CPU hogging browser ad-on
and "widgets" you cannot use on smartphone anyway
and a 1MB bigger SYS with otherwise identical packages
make not up for the option to be able to skin your menus, they just get bigger and making that finger friendly on smartphone is a joke
Sliding panels are in WM61 already (for those who like it) but I have my private homescreen that does all I want on one page and it includes ToDos which the Sliding panels does not.
Click to expand...
Click to collapse
I found one advantage WM65 over WM61 that maybe useful for some: WMPlayer shows embedded Album Art in WM65 while it does not in WM61. This includes the art display in the sliding panels Media Panel. I use Conduits PocketPlayer for years so never cared about this.
All OS Builder kitchen run well now (6.0, 6.1-Rose and 6.5-Captain). XIP porting was a little inconsistent across these versions but all startup and reboot without flaws.
Still have to cleanup the package sort order - at least in WM6.5 - and see if A2DP would work well (though it is a CPU hog and I would never recommend it).
Release may happen next weekend -> watch out for a dedicated thread then.
Best with the Hurricane cooking is that you will not have to care about ROM size and balancing with storage space on the device in 1 MB steps like on the Tornado - or be limited to fix size like on the Typhoon. The "l" (load) commend will trigger in the SPL a ROM-size matched formatting of the BINFS (in 64k steps, I guess).
Also "good" is that the device still has a RIL v1, so the Radio ROM is smaller (and less capable) then the Tornado Radio. You will hardly note the difference, however will NITZ (Time setting via GSM Network) not work with this RIL.
Even with 8MB Paging Pool (my default) you have free RAM of ~32MB (Sliding Panels Homescreen) or ~34MB with standard Homescreen. You could make the PP even 10-12 MB here and have the device even more "snappy" with several applications in parallel.
tobbbie Thanks for the good work!
I want also clean rom from FWUpdate, because in our phone it's not used, i some time make experiments with some files and when deleted one(i don't remember what file =((( )and it will free about 3 Mb Ram(on startup 35-36MB with sliding panels with weather =)), but i sometimes think, it's unbeliveble, because when i deleted that file, some system pictures don't work(etc. system notification) =(
I think the need to rewrite some system files in order to achieve this = (
No wild deletions, please. FWupdate is removed in the OSB kitchen and only one stub is left in WM6.1+ because otherwise the ROM does not work. Also some other packages are made optional (e.g. SQL mobile) - it so easy making something selectable with OSB (drag + drop), really fun to play with.
The OSB framework has sophisticated tools to analyse the dependencies, so a lot of insight to gain there. If you are curious, download my Tornado OSB Kitchen and do some dry-cooking, the Hurricane will be 98% the same. Also visit the main OSB kitchen thread to get the basic documentation.
Related
Hi all
I spend some time to optimize the cab-files in the extended rom.
I got rid of many bigger unnessesary files containing commercials and unneeded information. Some more
space could be saved by merging the registry - updaters into one file, here I also added the registry entries
to make the extended rom visible and to activate ClearType by default. Some install-directories for the links
have been updates to not overload "Programs" by default. The Homezone application is installed but will
not be added to the autostart folder. The CESetup.dll in the older cab files has been updated.
IACallerID is NOT installed, this app is so useless and consuming...
but thats my opinion.
The extended rom posted here contains some more application, from which I think, that they are rather a must.
This includes:
Bluetooth - Patch
PocketMVP 9 Which now supports the ATI graphic accelerator ( awesome performance... )
WakeupTweak
CheckNotificatiions
RegEditor
A file en-/ decryption tool to add some security
The "standard" files are the latest found in the t-mobile update, merged with the O2 customizition stuff.
The config.txt is up to date, but be aware the PocketMVP asks for a reset,
which must not be allowed.
The space left in the ext-rom is exactly enought for TOMTOM Navigator... but that's a different story...
My extended-rom displays 0.00MB left ;-)
I did not provide a .nbf file, if you need one please use the famouse ER2003edit.
Alex
User To User Tips, Tricks ideas and issues thread.
XDA_UC is a silent User & Cook automation script.
It requires no user configuration (unless you count dripping stuff into a folder as configuring).
It differs opposed to the default Autorun & RunCC configuration that, as a user you do not need no make an SDConfig.txt file on your SD card.
And that you can start using your device immediately.
It will run in the background at the reboot the Cook has chosen to have it run.
But it adds a lot of extra tweaking functionality for hardcore Tweakers to.
What it basically does is install the beneath on the user side
My.tsk file from "\Storage Card\XDA_UC"
and if not present Cook.tsk from Windows Folder.
Copy Over User Files.
Check for "\Storage Card\XDA_UC\Copy2Root" if present, Disable Manila from Homescreen then Copy files from "\Storage Card\XDA_UC\Copy2Root" to the root of the device, Then checking for existence of wallpaper_TF3D.png or wallpaper_TF3D.jpg in "\Storage Card\XDA_UC\Copy2Root\Windows" and adding that to
[HKCU\Software\HTC\Manila]
"HomeBackgroundPath"="\\Windows\\wallpaper_TF3D.jpg"
Import registry files from "\Storage Card\XDA_UC\Copy2Root\Windows\manila.reg" If present
Re-enable Manila on Homescreen and redraw it. Now also works for the Sense 2.1 and up versions.
.xdas files in "\Storage Card\XDA_UC"
Silently run Legacy SDConfig.txt from Storage Card
(If your using RunCC.exe or Autorun you do not need to point to or use SDAutorun.exe or SDConfig.txt) Thanks to RoryB
Commands for SDConfig.txt can be found here....
.cab files in "\Storage Card\XDA_UC"
.cab files in "\Storage Card\XDA_UC\Storage", These cab files will be tempted to install to Storage Location.
.cab files in "\Storage Card\XDA_UC\Manual",These cab files will start with Full User interaction capabilities to choose where to install to.
.reg files in "\Storage Card\XDA_UC"
.xml files in "\Storage Card\XDA_UC"
.mscr files in "\Storage Card\XDA_UC"
.cer files in "\Storage Card\XDA_UC"
Create Shortcuts and more from Registry Keys
More information here....
Copy over welcomehead.192.01.png & welcomehead.192.02.png present in "\Storage Card\XDA_UC\Copy2Root\Windows" to the Windows folder.
Copy over welcomehead.96.01.png & welcomehead.96.02.png present in "\Storage Card\XDA_UC\Copy2Root\Windows" to the Windows folder.
Actually everything is copied over from Copy2Root folder to root, but the above Splashcreens get their file atributes removed before this happens.
Add native support for .mscr, .mortrun, .xda, xdai, xdas & .xdaz files
This thread is meant for user to user help and advice and sharing of tricks and tweaks.
Cooks should go to http://forum.xda-developers.com/showthread.php?p=3954547 for more information about the cooking side.
I have attached a Mort Script HTML Manual for those looking into learn about this type of scripting.
Before you consider buying me a beer. Please consider Donating to XDA to help out with the maintenance of the forum and get cool stars next to your Nickname showing your appreciation. Then there are always the people that without their apps this wouldn't have been possible at all that you can consider showing some love. Mort, DotFred & Sleuth255 All of whom made Apps Seemingly simple But oh so useful for the whole XDA and PocketPC community.
Hopefully A List of Cooked Roms with XDA_UC Pretty Soon.
Give me holler,
Or my main Homie Moderator Ameet.
Or you can ask your Favourite Cook to look into this and incorporate it into his or her rom
A Lot of Energy Rom's
www.energyrom.com
ELF/IN
AHEN E6f
ETEN Glofiish M700
ahmedfikry wm6.5 23089 light rom
Kaiser
jjblaster3
Raphael
Noonski's Secret Nightly Rom, Simpel Pro Classic (deuh)
Rhodium / Touch Pro 2
Juicy R0 @ PPCGeeks
Bikeandestroy Rom
DavidMMorley's v1.5.3 @ PPCGeeks
Bhar'S 21891_V2/23540_V2
*7ppc* for TP2
Rhodium / Touch Pro 2 CDMA
xpressyourcell's XpressDusk @PPCGeeks
xpressyourcell's XYC GTX @PPCGeeks
Samsung Omnia
Rock and Republic WM6.5 ROM @ XDA
Rock and Republic WM6.5 ROM @ PPCGeeks
Storm's ROM [CF03] @ Modaco
MrCapcom's i910 6.5 Custom Rom CF03 Edition
TechMaster7545 WM 6.5 CF03 Rom Build 23009 For I910
FloTanium ROM
Sony Xperia X1
WM6.5 для X1 Rumanian
Topaz
EPS Creme RC2 DE
RTT Topaz Peak, RTT Topaz Peak @ XDA,
Touch Dual
DJ Series
Touch Cruise 2 / Iolite
Serfer222's Iolite WM6.1 (build 21055)
Serfer222's Iolite, WM65, Russian, XDA_UC (Official Russian Mega ROM ported to Iolite)
Serfer222's Kitchen + Iolite WM6.1 (build 21055) WWE
HD / Blackstone
BiCh0n's ROM (french)
Touch HD2/Leo
Merlion NG Leo v1.30's Merlion NG Leo v1.30
RTT Shock Star RTM GER
BiCh0n's ROM (french)
Trinity/P3600
nAr & Icke WM6.5[WWE][FRA][DEU]
NoseDive's n083 P3600+i
Common Good Practices
Do Not Reboot untill The XDA UC Message tells you it's finished.
You do not need to make your .cab files read only. But out of safety of loosing them it is recommended.
Save your .reg files as Unicode, always start your .reg file with
Windows Registry Editor Version 5.00
In the first line. And leave one blank empty line at the end of the .reg file.
Test your tweaks and files instead of reflashing to many times. A self initiated script will be uploaded soon, so you can test on a device.
Save your .xml files as Unicode and check if they are correctly formatted by opening them for instance in Internet Explorer.
If it doesn't show you the content then it will tell you where to look for mistakes.
More XML tips
Commands for SDConfig.txt for Version 2.0
AutoShortcut Registry Tricks
AutoShortcut Registry Tricks
HTC Autoshortcut replacment and enhancements through registry keys:
Directory Copy
Copy over files from one folder to another, overwriting the present files.
This will also copy over any subfolders inside the folder being copied over.
The entry on the left is the destination folder, the entry on the right is the source folder.
See the example code below:
Code:
[HKEY_LOCAL_MACHINE\Software\XDA\DirCopy]
"\\My Documents\\Test"="\\Storage Card\\My Documents\\Test"
You can also use this registry entry if you just want to make an empty folder.
See the example code below:
Code:
[HKEY_LOCAL_MACHINE\Software\XDA\DirCopy]
"\\My Documents\\Test"="MakeDir"
FileCopy
Copy just one file over from one folder to another.
The entry on the left is the destination File, the entry on the right is the source file.
See the example code below:
Code:
[HKEY_LOCAL_MACHINE\Software\XDA\FileCopy]
"\\My Documents\\MakeDir.reg"="\\Storage Card\\XDA_UC\\MakeDir.reg"
Delete
Delete a file. This will not delete Files in cooked in Rom/Windows folder.
But it will for instance delete Read Only Pictures in My Documents
See the example code below:
Code:
[HKEY_LOCAL_MACHINE\Software\XDA\Write]
"\\Documents And Settings\\Somefile.xml"=""
Deleting of a whole directory has not been added as mistakes can be made to easily, resulting in a complete Device and SD card whipe.
If you understand the risks I reccomend to learn writing your own mortscripts to do this.
Write
Write more explicit shortcuts or files
The left entry is the destination file, the right entry is the text you want written into the destination file.
See the example codes below:
Code:
[HKEY_LOCAL_MACHINE\Software\XDA\Write]
"\\Windows\\Start Menu\\Programs\\Tools\\TF Detacher\\icon.lnk"="50#MPI_ProgramIcons.dll,-115"
[HKEY_LOCAL_MACHINE\Software\XDA\Write]
"\\My Documents\\Somefile.txt"="Hello World"
Auto Shortcut Creation
To create shortcuts to files or applications.
The left entry is the target link name, the right entry is the source file the link should be pointing to.
See the example code below:
Code:
[HKEY_LOCAL_MACHINE\Software\XDA\AutoShortCut]
"\\Windows\\Start Menu\\Programs\\SAP Settings.lnk"="\\Windows\\SAPSettings.exe"
If you want to be sure that the destination directory exists where you want the shortcut created you can add an extra Registry entry for Directory creation.
See the example code below:
Code:
[HKEY_LOCAL_MACHINE\Software\XDA\DirCopy]
"\\Windows\\Start Menu\\Programs\\Contacts"="MakeDir"
[HKEY_LOCAL_MACHINE\Software\XDA\AutoShortCut]
"\\Windows\\Start Menu\\Programs\\Contacts\\SAP Settings.lnk"="\\Windows\\SAPSettings.exe"
Run First Boot
Run a file or application at the first boot.
The left entry if for the file or application, the right entry is for paramaters you want passed to an application.
See the example code below:
Code:
[HKEY_LOCAL_MACHINE\Software\XDA\RunFirstBoot]
"\\Windows\\btdwake.exe"=""
SDConfig.txt Commands
Commands that will work in SDConfig.txt
Be aware that for commands with only three letters there needs to be a space between the : & \
XML: \Storage Card\Cabs\Personal.xml
XML: \Storage Card\Cabs\Personal.provxml
(To parse provisioning .xml or .provxml files Saved to ANSI)
REG: \Storage Card\Cabs\G-Alarm.reg
(To parse registry files in Windows Registry Editor Version 5.00 format)
CPY1:\Storage Card\Cabs\pim.vol
CPY2:\pim.vol
(To copy over one file, and if pim.vol is found in Cabs folder, Cprog.exe will be shut down first)
MOV1:\Storage Card\Folder
MOV2:\Windows\Folder
(Aplied to latest Beta's, but this will copy over folders and it's subfolders overwriting any existing files)
SC1: \Storage Card\Program Files\GoogleMaps\GoogleMaps.exe
SC2: \Windows\Start Menu\Programs\Google Maps.lnk
(Simple Shortcut creation)
WR1: \A File.txt
WR2: The Text That Goes Into the File
WR1: \Windows\Start Menu\Programs\Tools\Another App.lnk
WR2: 99#"\Windows\SuperApplication.exe"?AnotherAppWithIcons.exe,-IDI_APPICON
Yes for the Advanced Users. It removes Files Attributes from possible target file then deletes it before writing a new one.
Note that there needs to be a space before the written text starts! (Special NoPrize for the one that knows which file was originally under "AnotherAppWithIcons.exe")
CER: \Storage Card\Cabs\Work.cer
(Install certificates)
CAB: \Storage Card\Cabs\098MSN.CAB
(Cabs that can be installed silently without user intervention)
SCAB:\Storage Card\Cabs\098MSN.CAB
(Cabs that you want installed to Storage Card)
MCAB:\Storage Card\Cabs\098MSN.CAB
(Cabs that you want installed with full user interaction)
EXEC:\Storage Card\Cabs\something.exe
EXEC:\Storage Card\Cabs\mortscript.mscr
EXEC:\Storage Card\Cabs\Or A Link.lnk
EXEC:\Storage Card\Cabs\Or A Even a document.doc (consider this to be a regular Open or Run file as long as the file is known by system but that can be set be doing a .reg first with the file open registry settings)
KILL:AutoVer.exe
(to close running open apps, be aware there is no Slash needed)
DEL: \My Documents\Picture\leaf.jpg
(Remove read write permissions then try to remove the file, will of course not work on ROM/Windows files)
TSK: \My Cool Theme.tsk
Apply Theme
RESET
Will set the Reset flag to force reset at the end of XDA_UC
Questions & Answers
Question:: I am a new user of Windows Mobile and I don't understand many of the terms here, can you tell me in a simple language what exactly XDA_UC is doing for me or for my device?
Answer: XDA_UC aplies and installs installation files and user tweak files in a simple and straight forward manner that does not lock up your screen as the regular Autorun method's would with out the need to know how to configure a pre setup SDConfig.txt file. It runs in the background and you can start using the device after flash (thought you will be a little slower at start uas stuff is happening in the background)
Or if above is still not easy to understand, let's say like this: After you flashed a new ROM, or did a hard reset (or you run 'Clear Storage' from system settings page, it's same as so-called 'hard reset' here), all your programs and your tweaks or adjustment to the Operation System is wiped out and you only have a clean OS from the firmware on your phone. At this time, XDA_UC will silently install all your programs and apply all your tweaks alltogether in a straight-forward way, and you don't need to install or apply them one by one. Provided onlyif you already placed the (cab installer & registry tweak) files in the designated folder.
Question::I noticed the advantage of XDA_UC. But as a newbie to this society, seems I can not take full advantage of it. Any simple guidelines about what shall I learn and where to start?
Answer: The best way is to start learning which Registry settings you want personally always to be aplied to any rom. Look for CeRegEditor 4.3 so you can study, dump and compare the regitry to find the specific Registry keys that you can then save as .reg files. Installing cabs is nice and takes away a lot of hassle put adding your own. It's also smart to just make a shortcut to a specific program you already have installed on your SD as most work fine onze they have been installed before. That should save time on installing some cabs.
Question:: I have some Greenware in my storage card, every time after flashing a new ROM or a hard-reset, I need to make shortcuts for them inside \Windows\Start Menu\, Can XDA-UC do that for me?
Answer: You can either add a registry String line to any .reg file you put into the XDA_UC Folder
[HKEY_LOCAL_MACHINE\\Software\\XDA\\AutoShortCut]
"\\Windows\\Start Menu\\Programs\\Synchro Time.lnk"="\\Storage Card\\Program Files\\Synchro Time\\Synchro Time.exe"
And XDAUC will at the end of process convert all these registry settings to real shortcuts.
Or make a mortscript with the line:
CreateShortcut(SystemPath("ProgramsMenu") \ "Synchro Time.lnk","\Windows\Synchro Time.exe")
Question: What if I want to run XDA-UC by myself? Is it possible? Since what time to run (on first boot. second boot, or which boot after hard-reset) is decided by the cook of my ROM.
Answer: A Script will be provided soon for this, but it won't install if files that have already been installed at the XDA_UC run at the first boot.
Almost everything that get's installed by XDA_UC is written to the registry so if someone has the time to develop a managing tool can read this values.
Coming soon...
Is this something that can be installed/added to an existing rom that I can use stand alone, or does it have to be cooked into a rom? Thanks.
In principle this is supposed to be a cooked in thing, but Once i have tested the V 1.0.02 fully, and tweaked the timing a bit i might make a trimmed down "Run Whenever you like version or add to a SDAutorun Only Rom"
But it the adding to SDConfig.txt will need some testing, that if no one else is doing i will need to test first someday.
Noonski said:
In principle this is supposed to be a cooked in thing, but Once i have tested the V 1.0.02 fully, and tweaked the timing a bit i might make a trimmed down "Run Whenever you like version or add to a SDAutorun Only Rom"
Click to expand...
Click to collapse
OK, thanks for the reply. I will keep monitoring this thread to see how you're doing. I'm thinking this is a good way to update after a flash, but I'm not sure if I want to change roms right now. Also, not too many roms have it cooked in just yet.
Is this to install to main memory only?
If not, how do we differentiate which cabs we want in main memory and which in storage card?
I'm testing the next version which will recognize the Cab's in an extra Folder "SD" inside of XDA_UC.
Cab's placed there will open with full user interaction, so you can choose the location of where to install.
And it already has a silent, and at least 40% more effective method then a cabfile, of installing whatever to where ever you want.
I will also in time, unless someone beats me to the punch, an example .xdas file, to which you can add, your own .xml, .reg, files & folders and an silent.mscr to.
You can add a lot to that, and do whatever you want, if your willing to say goodbey to cabs that is.
Noonski said:
I'm testing the next version which will recognize the Cab's in an extra Folder "SD" inside of XDA_UC.
Cab's placed there will open with full user interaction, so you can choose the location of where to install.
And it already has a silent, and at least 40% more effective method then a cabfile, of installing whatever to where ever you want.
Click to expand...
Click to collapse
What happens if your cab is NOT successfully installed? Is there an error trap of some sort or does the program just stop or crash?
Noonski said:
I'm testing the next version which will recognize the Cab's in an extra Folder "SD" inside of XDA_UC.
Cab's placed there will open with full user interaction, so you can choose the location of where to install.
And it already has a silent, and at least 40% more effective method then a cabfile, of installing whatever to where ever you want.
I will also in time, unless someone beats me to the punch, an example .xdas file, to which you can add, your own .xml, .reg, files & folders and an silent.mscr to.
You can add a lot to that, and do whatever you want, if your willing to say goodbey to cabs that is.
Click to expand...
Click to collapse
Yes we need a really functional, powerful and flexible XDA_UC. But it may be a challege to balance this:
For advanced users -> They can do whatever they want to do with the UC, and it's wonderful.
For common users -> They can use the basic functions of it without complex learning process, and later on they just will find more and more supprise out of it.
For this purppose maybe a readme file somewhere is also good additive.
dmcnado said:
What happens if your cab is NOT successfully installed? Is there an error trap of some sort or does the program just stop or crash?
Click to expand...
Click to collapse
Good Question, I'm going to fing a cab that doesn't want to install first
But it should not install and there is no error trap besides that the cab will not show up on the installed programs in the control panel.
After that it contiunues.
wg5566 said:
Yes we need a really functional, powerful and flexible XDA_UC. But it may be a challege to balance this:
For advanced users -> They can do whatever they want to do with the UC, and it's wonderful.
For common users -> They can use the basic functions of it without complex learning process, and later on they just will find more and more supprise out of it.
For this purppose maybe a readme file somewhere is also good additive.
Click to expand...
Click to collapse
That is the intention. With a growing amount of users not that into tweaking, i feel the urge to draw them in and start learning and then contributing.
Noonski said:
That is the intention. With a growing amount of users not that into tweaking, i feel the urge to draw them in and start learning and then contributing.
Click to expand...
Click to collapse
Vow, wondering what if M$ heard of this. Some big guy is inspirating everybody to hack their OS!
Joking. Thanks for everybody' efforts to push forward the development of WM system. I am one of those that inspired by this sociaty and just joined the team.
But basically I still keep the business way of thinking about some great apps or better methods. That is, some details and some promotion (marketing term) is always needed before it get reachable to every user and widely spreaded. I think I can contribute more on this aspect.
Edit: I added two more questions on post#4. Anybody can answer please answer.
Did my best to answer these.
And i updated the info in post 1 to reflect the updates in V 1.0.02
I added something to your answer, but still not feel satisfied. Please just keep editing it. What we need is just like an explanation you made on the Rapheal ROM thread.
Another thing is the title of these two thread (sorry I keep commenting on these off-topic issues):
[UC]XDA_UC V1.0.02, Automated & Silent User & Cook, Configuration Service[12/07/09]
&
[UC]XDA_UC Autoconfiguration User To User Thread[23-06-2009]
Maybe I'm a little slow, but I takes me more than 5 seconds to (not completely) figure it out what is this talking about after first glance at the title, and then decide to take a look inside.
And then look at another big guy Menneisyys's thread title:
Sticky: Another revolutionary utility by me: add "find in page" support to most web browsers!
It is completely different effect on grasp reader's notices. And that makes difference on spreading speed.
Just comment, no matter is you insist to keep Noonski style.
wg5566 said:
Another thing is the title of these two thread (sorry I keep commenting on these off-topic issues):
[UC]XDA_UC V1.0.02, Automated & Silent User & Cook, Configuration Service[12/07/09]
&
[UC]XDA_UC Autoconfiguration User To User Thread[23-06-2009]
Maybe I'm a little slow, but I takes me more than 5 seconds to (not completely) figure it out what is this talking about after first glance at the title, and then decide to take a look inside.
And then look at another big guy Menneisyys's thread title:
Sticky: Another revolutionary utility by me: add "find in page" support to most web browsers!
It is completely different effect on grasp reader's notices. And that makes difference on spreading speed.
Just comment, no matter is you insist to keep Noonski style.
Click to expand...
Click to collapse
Is that really important? In my opinion the answer is no.
Noonski! Thank you for your Great work on this, i have included this in my rom and with Blazing Wolfs help got it up and running with no issues, except one.
Whenever i set XDA_UC to start of first initial flash it kills my modem i have to manuly pick the network the my phone uses to connect to the internet. IF i make XDA_UC start after a reboot it works perfect, I have tried to look at all The MSRC files and cant see to put my finger on the issue!!! Thanks in advance!!!
This is a port of the excellent Da_G Fuze (GSM) Kitchen. It has been fully modified to work on all CDMA Touch Pro's. I personally have a Sprint Touch Pro.
Da_G has been gracious enough to consider this the "CDMA Version" of his very popular kitchen. Without his help over the past two weeks, I would have never been able to get the new Bepe (Ervius) style kitchen working. I also received a lot of initial help from MightyMike. His kitchens and personal OEMs are what got me started. So, here are the usual "thank you's":
Da_G, MightyMike (PPCGeeks), Bepe, Ervius, Dan-HTC-Touch (PPCGeeks), Tsowen, Showaco, TPlane37, Calkulin
If I have forgotten to mention you in the above list, don't worry, I didn't forget about you. (Wait, yes I did.) But, please send me a message so I can add you to the list!
Information on where the Kitchen was built from:
SYS: Da_G
XIP: Da_G
OEMs: MightyMike, Da_G, Tsowen (Taskbar), Showaco (Titanium Weather), Me
EXTs: Same as OEMs list
Kitchen Design: Da_G modification of Ervius' base kitchen based on Bepe's new style kitchen (PlatformBuilder)
CHANGELOG:
Thursday (14-5-2009)
Updated SYS to 21231
Updated XIP to 21231
Updated Ervius Visual Kitchen to 8.0
Restructured the <EXT\SHARED>. Left all SYS in SYS. No more PhoneComponents in EXT.
Monday (11-5-2009)
Updated AdobeFlashLite
Updated RemoteDesktop
Updated Widgets
Updated Windows Update
Titanium Pictures tab open HTC Album by default (if Album installed)
Added Notification Enhancement (Rhodium/Topaz)
Added Custom Round Icons for NE
Added New Round Taskbar Icons
Added PowerOff Warning to match NE
Added White NonS2A Dialpad Skin to Kitchen (No ROMS built with it)
Updated GoogleMaps to 3.0.1.6
Updated HTC Zip to 1.21.18193225.0
Added G-Alarm 1.5.1
Added SmartLock 1.7C by Chobit Company
Resolved XIP Issue for VZW TouchPro's
Dropped SPRINT FULL from Pre-built ROMs
Dropped ALL CDMA Carriers Basic from Pre-built ROMs
Added SprintTV and Sprint NAV to CABs (Still in Kitchen)
Dropped QuickGPS from Pre-built ROMs (Still in Kitchen)[
Updated HTC MenuEnhancement to 1.0.19123021_01
Added 3 Sizes to HTC MenuEnhancement (ExtraSmall, Small, Medium.. You MUST Choose one if using Kitchen and ME)
Wednesday (6-5-2009)
Updated SYS to 21222
Added ATContacts
Added CHome Editor
Updated Titanium Weather to 4.2
Updated Mortscript to 4.3b5
Added Option for 4 Column Start Menu in Kitchen (Included in ROMs)
Minor Registry Tweaks
Monday (4-5-2009)
Updated SYS to 21502
Updated to Ervius 7.6
Changed Organization of EXT Folder per this update
Fixed multiple build errors that were being suppressed
More accurately diagnosed and corrected "Corrupted Ringtone" errors
This should fix the silencing of sounds/notifies randomly
Were some memory overlaps in a key module
Fixed Teeter
Minor Registry Tweaks here and there
Added many different "pre-built" roms.
Each of these have a ".erv" file. Look in "Load ROM"
Look below the screenshots for the Comparison Table
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Stable enough for every day use? Well, I am (Yes, I stole this from Da_G, BUT, I REALLY AM USING IT DAILY!)
Instructions for Pre-Built ROM Flashing (Via PC)
Step 1. Be sure your phone is Hard SPL unlocked and ready for a ROM. (Check the link at the bottom of this post).
Step 2. Extract your desired ROM to a clean folder.
Step 3. Connect your phone to PC via USB (Make sure ActiveSync/Mobile Device Center goes connected).
Step 4. Run Custom_RUU.exe in the folder you extracted the rar to.
Step 5. Follow the on-screen instructions.
Step 6. Wait for entire Windows Mobile customization process to complete and phone to soft-reset.
Step 7. Hard Reset. (Start->Settings->System->Clear Memory)
Step 8. Wait for entire Windows Mobile customization process to complete and phone to soft-reset.
Step 9. Job done!
Instructions for new style kitchen (build 21501 and above)
Step 1. Extract to a clean folder
Step 2. Run erviuskitchen.exe
Step 3. Click "load rom"
Step 4. Choose "dB_ROM-21501"
Step 5. Scroll down to section labelled "HERMAN-Device: HERMAN_External_Packages" in blue text
Step 6. Double click packages here to enable or disable them (first column reads True for enabled, False for disabled) (Leave alone for Defaults)
Step 7. Do the same for section under that labelled "SHARED-Devices: WindowsPhone_Components" as step 6 (Leave alone for Defaults)
Step 8. (Optional) Click "Save ROM" and choose a filename, to save your package choices for loading in the future
Step 9. Click "Create ROM"
Step 10. ROM is available in .nbh form in kitchen folder \HERMAN_RELEASE, you can either flash it with the included RUU.exe or rename to RAPHIMG.NBH and place on fat32 formatted SD card, for SD flash
General Notes for ROM and Kitchen
Always hard reset after initial flash. (I always wait till Autorun/SDAutorun complete and device soft resets)
Soft reset after hard reset doesn't hurt anything. (Comes from my old Titan days)
Don't worry about all the "Overwriting..." in the kitchen build process. It's normal and expected.
DO NOT use XIP 21502 in Kitchen. It's broken. I know what it is, but there is no change from the 21501 XIP, so just use it.
Report all bugs, etc here. Da_G and I have worked hard to make this as bug free as possible, but, Shhhtuff happens.
Don't blame me if you brick your device. It's not my, or the kitchens, fault. You recognize the potential problems that can arise from flashing your own ROMs on your phone. Da_G and I will take no responsibility. "Use at your own risk."
All that being said, I have had no issues during flash processes. I use this as my daily phone and have no ill side effects.
Before you Begin
If you have never flashed a ROM before, PLEASE read the information posted by egzthunder1 in the sticky thread of this forom. You must first unlock your SPL. All the information on doing this has been gathered and placed in a easy to follow step-by-step guide in the thread. Here is the direct link.
Download Links21231 VGA WWE ROM - Full - ALL CDMA Carriers - Beta 1
21231 VGA WWE ROM - No Manila - ALL CDMA Carriers - Beta 1
21231 VGA WWE ROM - BareBones - ALL CDMA Carriers - Beta 1
21231 VGA WWE Kitchen for Touch Pro (CDMA) - Beta 1
21222 VGA WWE ROM - Full - ALL CDMA Carriers - Beta 2a
21222 VGA WWE ROM - No Manila - ALL CDMA Carriers - Beta 2a
21222 VGA WWE ROM - BareBones - ALL CDMA Carriers - Beta 2a
21222 VGA WWE Kitchen for Touch Pro (CDMA) - Beta 2a
21502 VGA WWE ROM - Full - Sprint Optimized - Beta 1
21502 VGA WWE ROM - Full - ALL CDMA Carriers - Beta 1
21502 VGA WWE ROM - No Manila - ALL CDMA Carriers - Beta 1
21502 VGA WWE ROM - Basic - All CDMA Carriers - Beta 1
21502 VGA WWE ROM - BareBones - ALL CDMA Carriers - Beta 1
21502 VGA WWE Kitchen for Touch Pro (CDMA) - Beta 1
21501 VGA WWE ROM for Sprint TP - Beta 1
21501 VGA WWE Kitchen for Touch Pro (CDMA) - Beta 1
Known Issues:
21501
Teeter not installing properly. (FIXED - CAB removed, PM if needed)
Alarm Sound not working (Appears in ALL CDMA 6.5 ROMS)
Sounds & Notifications getting "Ringtone is Corrupt" randomly. (Semi-Fixed in 21502 release)
Default "CallerID Bubble" showing up with S2A, S2A wins battle.
21502
Alarm Sound not working (Appears in ALL CDMA 6.5 ROMS)
Default "CallerID Bubble" showing up with S2A, S2A wins battle.
Sounds & Notifications getting "Ringtone is Corrupt randomly. (Resolved with 21222 SYS)
21222
Alarm Sound not working (Appears in ALL CDMA 6.5 ROMS)
Default "CallerID Bubble" showing up with S2A, S2A wins battle.
21222 Beta 2a
Alarm Sound not working (Appears in ALL CDMA 6.5 ROMS)
Default "CallerID Bubble" showing up with S2A, S2A wins battle. (Issue with HTC Dialer, NO ETR)
SmartLock is very slow. Only have it in ROMs/Kitchen for testing. It's installed but not enabled in ROMs.
Fixes:
21501
Teeter not installing EXE or MUI file - RS DOWNLOAD - CAB Removed, PM if needed.
21502
Borked the "RomSaved" folder in the kitchen. If you downloaded the Kitchen prior to 02:02 CST on May 4, 2009 (Or you look in <TOOLS\RomSaved> and you only have one .erv file), you need to download the <RomSaved.zip>. Extract the contents to your <TOOLS\RomSaved> dir. PM If needed.
21222 Beta 2
MenuEnhancement Skins are Borked (FIXED - Download CAB below or Download new 2a ROM/Kitchen above or 2 to 2a Kitchen Upgrade below)
DeCiBeL_MenuEnhancement_Medium.cab - Standard size for HTC Menu Enhancements
DeCiBeL_MenuEnhancement_Small.cab - Half way between Standard size and 11 items in portrait.
DeCiBeL_MenuEnhancement_ExtraSmall.cab - 11 Items in Portrait.. My fave! This will be the one included in ROMs.
21222 Beta 2 to Beta 2a KITCHEN Upgrade - READ THE README IN THE RAR!!
Extras:
Attached ATContacts in cab form, per request. Included in Kitchen/ROMs now.
Facebook Offical Release v1.0.0.7
Tsowen's WM6.5 Taskbar (Pretty Icons)
Cab to Change to 4-Column Start Menu
Cab to Change to 3-Column Start Menu
How To Create EXT Packages for New Style Kitchen:
Download the EXT_Package_Tools.zip below and extract the two exe files inside to the <TOOLS> folder of the Kitchen.
If you have a cab, run Cab2OEM.exe on it first. Otherwise, goto step 3.
Run EXT_Packages_Rebuilder.exe on the OEM Package directory.
Place the resulting folder in the <EXT\Herman\Common\*> Directory it belongs in.
Example:
Open two explorer windows. Have one window open to the <TOOLS> directory of the Kitchen. Have the other window opened to the directory containing your CAB or Original OEM Package.
Now, if its a CAB, drag the CAB file and drop it on top of Cab2OEM.exe. This will open a command prompt and close it. You should now have a folder in the Explorer window containing the CAB file.
Make sure the folder contains all the files, including the *.rgu file, etc. Now Take that entire folder and drop it on top of EXT_Packages_Builder.exe (Drag the Folder, not the files inside, but the ROOT folder). This should restructure the Folder created in step 2 to have a <files> folder inside of it that contains all the files for the Package, including any .provxmls. There will also be an <app.dat> and <app.reg> file (if applicable). The <app.dat> is the old "initflashfiles.txt". The <app.reg> is the old "*.rgu".
Now check the reg file and make sure it looks setup properly. Cab2OEM.exe likes to bork registry files sometimes. So I would look over this carefully. After you're sure its good, move the folder to the appropriate area in <EXT\Herman\COMMON>. Load up your fav ROM pref from my Kitchen. Scroll down to your package and make sure its "TRUE". Cook and be done.
EXT Package Folder Structure:
<Root Folder> - Name of Package
--<files> - Folder that contains all files that will be installed to \Windows
--<app.dat> - The old <initflashfiles.dat>, contains instructions to copy files, etc.
--<app.reg> - Contains all registry entries for the Package.
djbeames said:
Gotta have pizza to go with that Keg....
Click to expand...
Click to collapse
You should enjoy that keg mate. Good work I did wonder when you would be bringing this kitchen out after noticing your posts in the original thread (I own a GSM Raph but have been thinking of cooking roms for CDMA aswell and wasnt sure if it was possible).
EDIT: Oh yeah, I have quite a good copy of Xboxmods new Manilla port in EXT packages if you want a copy that works in this kitchen
B4PJS said:
You should enjoy that keg mate. Good work I did wonder when you would be bringing this kitchen out after noticing your posts in the original thread (I own a GSM Raph but have been thinking of cooking roms for CDMA aswell and wasnt sure if it was possible).
EDIT: Oh yeah, I have quite a good copy of Xboxmods new Manilla port in EXT packages if you want a copy that works in this kitchen
Click to expand...
Click to collapse
I have been debating adding XBoxMod's TF3D2 for a while now. I have seen it cause some issues in other kitchens, so have been very skeptical of adding it until more stability is shown.
However, I wouldn't mind throwing it in my test kitchen and firing off a test build to see how it runs for a day or two. Getting off TF3D and onto TF3D2 (Rhodium!!) would be my next logical step, and very much worth it.
The reason it took so long for me to release this is my own perfectionism. I can't stand to release something that isn't nearly flawless. I have had it "almost finished" for about a week. Then I would notice another issue and have to fix that. Then another, and another. Most were very minor (sounds would not list properly in settings, mortscript wouldn't delete from autorun, provxml's would backfire, etc). I finally set a goal of having it released by this weekend, regardless of status. Luckily I feel this is in great shape as most of the issues I have found are resolved.
Thanks for the support!
djbeames said:
Gotta have pizza to go with that Keg....
Click to expand...
Click to collapse
djbeames said:
I have been debating adding XBoxMod's TF3D2 for a while now. I have seen it cause some issues in other kitchens, so have been very skeptical of adding it until more stability is shown.
However, I wouldn't mind throwing it in my test kitchen and firing off a test build to see how it runs for a day or two. Getting off TF3D and onto TF3D2 (Rhodium!!) would be my next logical step, and very much worth it.
The reason it took so long for me to release this is my own perfectionism. I can't stand to release something that isn't nearly flawless. I have had it "almost finished" for about a week. Then I would notice another issue and have to fix that. Then another, and another. Most were very minor (sounds would not list properly in settings, mortscript wouldn't delete from autorun, provxml's would backfire, etc). I finally set a goal of having it released by this weekend, regardless of status. Luckily I feel this is in great shape as most of the issues I have found are resolved.
Thanks for the support!
Click to expand...
Click to collapse
These are the packages that I cook by default into my ROM. The main thing with this kitchen is that it seems to crash when you try overwriting a module with a file, in TF3D2 there is a taskmanager.exe that tries to replace the original module which is why the kitchen dies when cooking, in my version I have just removed the exe and all works fine
EDIT: Here is the link!! TF3D2_EXT_Package
Is there any way you can make this an installable RO for the Fuze? I know it's a kitchen, but the only computers i have access to are the ones at work at this time, and I don't want to install anything to them. I love the taskbar icons!
BTW - what color is the selected items?
Thanks in advance
xombi said:
Is there any way you can make this an installable RO for the Fuze? I know it's a kitchen, but the only computers i have access to are the ones at work at this time, and I don't want to install anything to them. I love the taskbar icons!
BTW - what color is the selected items?
Thanks in advance
Click to expand...
Click to collapse
Check the first post...
21501 VGA WWE ROM for Sprint TP - Beta 1
And then you just need to find the keyboard fixes for the Fuze
B4PJS said:
Check the first post...
21501 VGA WWE ROM for Sprint TP - Beta 1
And then you just need to find the keyboard fixes for the Fuze
Click to expand...
Click to collapse
Uh... you can't just flash a Sprint ROM to an AT&T phone. Doesn't work like that. One is GSM, other is CDMA.
Someone else correct me if I'm wrong.
xombi said:
Uh... you can't just flash a Sprint ROM to an AT&T phone. Doesn't work like that. One is GSM, other is CDMA.
Someone else correct me if I'm wrong.
Click to expand...
Click to collapse
Ummm, we ARE in the CDMA thread....
Why isn't this posted in the CDMA section then?
This section is designated for GSM phones only.
B4PJS said:
Ummm, we ARE in the CDMA thread....
Click to expand...
Click to collapse
Are we? This thread should be in the Raphael CDMA Forum.
xombi said:
Why isn't this posted in the CDMA section then?
This section is designated for GSM phones only.
Click to expand...
Click to collapse
gmgonzal said:
Are we? This thread should be in the Raphael CDMA Forum.
Click to expand...
Click to collapse
I stand corrected. Mod's, please delete this post. Thank you scotchua!
Thanks for the contribution to the CDMA side of things =)
Wrong thread
I see bad things happening with this being in the GSM forum. I see nebies flashing this to their Fuze and bricking there phones. This should be moved to CDMA. One quick question why do we have a CDMA forum and a separate GSM forum if we are going to allow CDMA in the GSM forum.??????????
hopalongis said:
I see bad things happening with this being in the GSM forum. I see nebies flashing this to their Fuze and bricking there phones. This should be moved to CDMA. One quick question why do we have a CDMA forum and a separate GSM forum if we are going to allow CDMA in the GSM forum.??????????
Click to expand...
Click to collapse
I stand corrected. The moderator's have spoken and this thread has been moved to the proper location. Now if they can clean off the "Wrong Forum" posts, we'll be in business!
Thank you for so forcefully pointing out it was in the wrong location. The Forums for the Raphael area a bit misleading.
I don't mind being the guinea pig on this. I'm having some issues with Mighty Rom 5 anyways, so hopefully this ROM addresses some of those. Any known issues? Thanks!
P.S. If this ROM bricks my phone....watch your back. j/k.
btw: I have a Sprint Touch Pro
----------------------------------------------
Edit:
Just got done flashing and hard resetting. So far, so good. I like the fact that Titanium Weather is already installed. Any chance of getting ATContacts in the ROM? I know I can install it, but I'm just saying... Thanks!
djbeames said:
I stand corrected. The moderator's have spoken and this thread has been moved to the proper location. Now if they can clean off the "Wrong Forum" posts, we'll be in business!
Thank you for so forcefully pointing out it was in the wrong location. The Forums for the Raphael area a bit misleading.
Click to expand...
Click to collapse
@djbeames
Good work, pal! Now, considering the amount of misinformation floating around in the whole Raphael section, you may want to link to my first post in this section (This Sticky). This contains all the needed stuff to HardSPL and flash the roms. I know that you are familiar with PPCGeeks, but a lot of poeple aren't, so giving them instructions on how to do it will probably save a few people from either bricking their devices or simply from posting questions such as "how do I put this in my phone?"
Again, good work and it is great to finally see some Chefs in the Herman section !
Great work, linking from my thread
afripino said:
I don't mind being the guinea pig on this. I'm having some issues with Mighty Rom 5 anyways, so hopefully this ROM addresses some of those. Any known issues? Thanks!
P.S. If this ROM bricks my phone....watch your back. j/k.
btw: I have a Sprint Touch Pro
----------------------------------------------
Edit:
Just got done flashing and hard resetting. So far, so good. I like the fact that Titanium Weather is already installed. Any chance of getting ATContacts in the ROM? I know I can install it, but I'm just saying... Thanks!
Click to expand...
Click to collapse
Thank you for trying it! But, trust me, you are NOT the guinea pig. I have my wife and my touch pro's I try it all on first. Then I have a couple friends that also have them. Between the 4 to 5 of us, we thoroughly test it all. I have been developing this initial release for quite some time now. See below...
Btw, let me know how it goes. I'm here to fix things and make improvements and adjustments. As far as ATContacts is concerned, hit me up with a link and I will check it out. At the very least I might add it to the kitchen as an external package.
egzthunder1 said:
@djbeames
Good work, pal! Now, considering the amount of misinformation floating around in the whole Raphael section, you may want to link to my first post in this section (This Sticky). This contains all the needed stuff to HardSPL and flash the roms. I know that you are familiar with PPCGeeks, but a lot of poeple aren't, so giving them instructions on how to do it will probably save a few people from either bricking their devices or simply from posting questions such as "how do I put this in my phone?"
Again, good work and it is great to finally see some Chefs in the Herman section !
Click to expand...
Click to collapse
Consider it done. As soon as I get home for the evening I will post more information in the OP and link to your sticky. Thank you for pointing it out.
Edit: Done. XDA was down all night, so I didn't get it added until this morning. Thank you again for putting that info together. Good documentation.
Da_G said:
Great work, linking from my thread
Click to expand...
Click to collapse
Yep. We finally did it, eh Da_G? Thanks for all you have done on this kitchen. It truly is because of your willingness to share, this has been released.
Let's make HD2 the best Windows Phone 7 device
My tutorial on porting WP7 sys (and update to NoDo) for HD2 is in my 2nd post, you'll find too my tricks and ideas
Thanks to Ruzzichella, DFT, bepe, cotulla, ervius, AnDim, Nokser, ansar, OndraSter, airxtreme, misar etc. etc.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
16/05 First release:Porting HD2 WP7 rom to NoDo (see 2nd post)
New theme with transparency I've called Aero
HTC Hidden Wi-Fi works since I've updated some OEM packages. To have a wifi mac adress which don't change at reboot try to set it in the nvram.txt file (see my second post)
Rom is unlocked and prevented to relock.
A video demonstration: Youtube_WP7_NoDo_ROM_HD2 (thanks Jaxbot)
05/06 Update:Green key is now hard remaped, I've chosen the function of bluetooth Headset: Play/Pause multimedia, Skip by pressing twice, Answer a call (when receiving), End call, (when in call), long press to rapidly call someone by speech input.
Replaced camera button by a software button with autofocus like on Androïd so no more blur.
Radio is working without the need of headphones.
Added keyboards layout for some other countries and added some cool features. More layouts to come soon.
Improve performances, localisation (assisted gps - agps), Bluetooth, battery consumption. (mine is between 3 and 6 mA)
Solving of certains difficulties to establish a link with some Wi-Fi routers.
Smooth gradients (no more 16bit banding bug) without lost of performances.
Backlight adjusted and set to never by default (work have to be done)
Changed volume settings and added a sound template to make it more clear.
Replaced all Microsoft and OEM wallpapers by transparent png, so a total of 41.
08/06 Update:Replaced all overlaped modules of the 7392 base rom, so improve about everythingSpeech recognition (long press Win key and Call contact Green key) works for every languages
13/06 Update + 16/06 minor Update:Added direct access to Wi-Fi and Bluetooth in start menu and home tiles.
Added direct acces to Airplane mode and Brightness (16/06)
Update of the HTC RIL manager module and added the last HTC Connection Setup for autodata config at boot.
Added keyboard layouts but there is a limitation of 20 keyboards so I split the rom in 2.
Added some other long press on keyboards layout ie w->www. f->ftp://ftp. (16/06)
23/06 + 26/06 Update:Rom is rooted now (first WP7 rooted rom)
Optimisation of the policy database for root access (+live games fix) (26/06)
Added direct acces to Cellular and Location
Added direct acces to Sound and Lock and changed all icons added to real metro theme (26/06)Added 2 extra themes (Aero variations with transparency): Aero Black and Aero RichThe Rom Files: v5_lang1 and v5_lang2 - These are the roms, no language pack!!! see below
Rom is split in two versions with differents keyboards layouts
In both: Spanish, French/Canada/Swiss, German, English US/UK, Italia
Lang1: Finish, Hungarian, Swedish, Czech, Danish, Dutch/Belgian, Norwegian, Polish, Poruguese/Brazilian, Filipino
Lang2: Turkish, Malay, Arabic(as Ecuador), Hebrew(as Uruguay), Farsi(as Bolivia), Chinese, Greek, Korean, Russian, Indonesian, Ukrainian, Thai(as El Salvador)
A xap to give back the 3rd option speaker/headset in FM radio (but you'll need Headphones): ProvXml-FMradio.xap (thanks to xboxmod, for use see his thread)
A pack with all HD7 radios (files part00.bin to replace in Data.zip before flash): HD2 WP7 radios pack
If you want another hard keys remaping template see here
If you like my work, don’t pay me a beer, don’t thank me but just send as much “MISS U” as you want to +33 682732382 (France)
Tutorial to port sys (update to NoDo)
Ok guys, I don’t know why DFT haven’t release an update for HD2 earlier since it take only few days to a noob to achieve a working NoDo rom. Their first version was built on a test rom with developer’s certificates from Microsoft and HTC, debug tools, recompiled drivers for HD2 and a method to build SLDR and NK sections. They had before everybody a test version of Mango too. So I suppose they, or only one, is working for HTC or has good contacts and perhaps had a commercial interest or was more interested by the exploit than giving users a great experience of WP7 on HD2, updates as soon as it’s possible and tools/knowledge to members like ervius, AnDim, Nokser etc. to achieve that by themselves. Someone in another post suggest an agreement not to release their mango before the 24th, it’s quite possible. But I don’t know and I don’t blame, it’s life lol
Perhaps we’ll see a version of Mango for HD2 soon (and new exiting videos^^’) but since a lot of people are waiting for NoDo (some desperate posts made me cry XD) I’ll give you a first version, and better, the method to achieve that by yourself for the next coming.
!The trip isn’t how to flash an HD7 rom on HD2 like certain people seems to believe and we don’t need a new malgr for the moment!
What you need:
DSM editor by Ervius http://forum.xda-developers.com/showthread.php?t=523139
WP7 Rom Tools by AnDim http://forum.xda-developers.com/showthread.php?t=884239
IMGFSFromDump-TURBO by airxtreme http://forum.xda-developers.com/showthread.php?t=610713
Imageinfo.bin, packages.cif/sof Tool by kokotas http://forum.xda-developers.com/showthread.php?t=674477
DFT rom and DWI by by bepe and Cotulla
A rom with 7392 SYS like RUU_Mozart_TMO_DE_1.32.111.01_5.65.09.25_22.45.50_ RELEASE http://forum.xda-developers.com/showthread.php?t=1065281 (MOZART is not important for SYS parts)
Some extra roms for updated other SYS languages
A rom with latests HTC packages to have the possibility of stuff like Hidden Wi-Fi like RUU_Schubert_O2_DE_3.04.207.01_Radio_5.66.09.21a_2 2.48.50.21 http://forum.xda-developers.com/showthread.php?t=1037967
Optional:
A rom for a new radio, this one seems to be the latest too
A rom for developpers tools and kitl like RUU_Schubert_hTC_Asia_SEA_WWE_1.57.728.02_Radio_5.52.09.16_22.33a.50.10_TEST
Roms for OEM APPS stuff that you want
A good HEX editor and a file/directories comparator may help a lot
Just a little time and patience lol
PS: open roms with an archive tool like 7-Zip and take the RUU_signed.nbh file, we only need this.
1. A new radio: (optional)
The radio is the part00.bin in the Data.zip
With HTCrie open the nbh which contains the radio you want, select GSM and extract the GSM.nb
Open it with an hex editor and search for 7F 45 4C 46 01 01 01 61, it’s the beginning of the part we need. The end is the series of 00 just after the last AMSS string you can find (refer to DFT part00.bin if you need help).
Keep only this section (delete the rest) and add some 00, for example if the files ends at the byte e004d0h go to e004ff.
Save the file, rename it part00.bin, you’ll have your new radio (in this case 5.66.09.21a).
Replace it in the Data.zip, you can flash now with DWI to test it.
You’ll show the new version in the Settings/About of WP7.
2. Change The SYS by 7392 Step 1: Common packages
With HTCrie open the nbh which contains the 7392 SYS build (or another you want), extend OS/IMGFS and select SYS. Extract it to a folder.
Do the same for other rom(s) containing extra languages in another folder.
Add the extra *_LANG_0XXX packages from the second directory to the first, after that you can delete it (the second folder lol, if only English was my native language^^).
You can use NabSync and NabSync_Lang_0XXX packages or not, if not delete them, just remember you’ll not need to add MOS entries in default.hv in this case.
Put the metadata package in another place, we’ll use it in step 2.
Put the content of all other packages in a new folder (for ex called IMGFS), with HTCRIE open the same 7392 rom, extend OS and in IMGFS content select .ROM and .VM modules, extract them in your IMGFS folder.
It’s your new SYS.
You could past/overwrite it in DFT IMGFS and build the rom now it will function (the DFT video of March) and YES it’s as simple as that, you’ll have new stuff from NoDo like copy/paste but not the possibility of Hidden Wi-Fi since it depend of OEM packages.
PS: It’s possible since there isn’t many changes in NK and SLDR sections made by NoDo, so we can use like that. dsm files are not very important (just to have good references of packages) and rgu content is added in default.hv
Modules that need to be updated are:
NK: cachefilt.dll, hd.dll and osaxst0.dll
SLDR: exfat.dll, filesys.dll, k.coredll.dll, k.fatutil.dll, kernel.dll, mtpuldrsvc.dll, pm.dll, sdbus.dll, sdmemory.dll and unifiedblock.dll
3. Change The SYS by 7392 Step 2: metadata package
With HTCrie extract the metadata package of the SHUBERT rom which contains OEM that you need, so we have to play with 3 metadata packages: DFT, SHUBERT OEM, MOZART SYS.
It could be a little simpler if we have a 7392 rom for SHUBERT but not for the moment.
Some files need to be updated, first is BasePolicy.xml, compare the new content of MOZART with DFT one, same for SCHUBERT (replace C:\WM700\release\LEO and C:\WM700_7392\release\MOZART by C:\WM700_7392\release\SCHUBERT). If you find new entries and you judge them useful (refer to dsm and find the package) then add them in MOZART one (it’s the most important for SYS).
Second is DefaultCerts.dat, these files contain certificates. In hex each one begin with 30 82 ?? ?? 30 82 so you can cut this file in x parts, one for each certificate.
The common build is Microsoft root, oem roots, Microsoft Windows Mobile PCA0, oem, Microsoft Mobile Device Unprivileged PCA0.
We’ll keep DFT one as bas as it’s include Qualcomm infrastructure development, Microsoft Corporation CE Image Update Test and HTC_Develop_Test, useful for later (we never know^^). DFT has included HTC_Develop_Test twice (like in dsm beside Microsoft Corporation CE Image Update Test) so you can remove the second.
What you need is to take DefaultCerts.dat from other metadata packages, extract OEM 168 or/and OEM 169 (personally I’ve included both from other roms so I’ll never have to touch this file again) and insert oem/oem root certificates in DFT one.
packages.cif and packages.sof are certainly updated but you can edit them with Imageinfo.bin, packages.cif/sof Tool.
Compare the imginf.txt you obtain for each roms you use (you can sort this file to make it more simple).
Like with BasePolicy.xml, if there is an entry that you judge useful, just add it in packages.cif and .sof (refer to this tool’s post in forum to know how use it well, but it’s quite simple).
The last two files but more important are default.hv and user.hv
To edit them just drag them onto HVEdit.exe by AnDim, you’ll obtain default.hvm and user.hvm which can be edited like rgu files.
To rebuild hv just drag hvm onto HVEdit.exe
I suggest keep the 7392 ones as base, compare them with DFT originals and modify entries you want.
For some you need a little knowledge (refer to forum) but for most it’s language entries and some tweaks.
You can refer to rgu files which differ and take a look at NoDo and 7392 pku to know which files/rgu are concerned (see forum to know how obtain pku for each zune update and extract them but don’t use files as they are in your build since most of them are not suitable (except dsm), they only contain information to update files/modules)
You can add for exemple your LiveID useful for HD2 users:
Code:
[HKEY_LOCAL_MACHINE\Software\Microsoft\GwpCPC]
"ActivationCode"="77777-77777-77777-77777-77777"
Copy the content of the new metadata package in your IMGFS folder. Now you have a fully functional SYS that you can use instead DFT one Let see OEM packages.
4. Change OEM packages Step 1: common packages
With HTCrie extract in two folders (like for SYS before) the OEM packages, one for DFT (for most you’ll find them at the wrong place: in SYS - like for most of TEST roms you can find) the other for the rom with most updated HTC packages.
You don’t need HTC_8x50_OS_UI_LEO as we replace it by HTC_8x50_OS_UI_SCHUBERT
You don’t need StartKitl and kitl.dll from DFT as it’s debug tool (we’ll see later) and HTC_CSPOSDrivers is new stuff so don’t search it in DFT rom.
Other packages which can be used without modification beside HTC_CSPOSDrivers are CSConn_DB, HTC_Global_Customization, OEM_8x50_BLDR, OEM_8x50_BSP, OEM_8x50_LOGO, OEM_8x50_MODEM, QC_8x50_OS_MM_CFG_2 so just delete them like for HTC_8x50_OS_UI_LEO in DFT folder to see more clearly.
5. Change OEM packages Step 2: updated packages
Like I’ve said we could use DFT OEM packages as they are but we won’t have new stuff from HTC like Hidden Wi-Fi. So we have to update some modules.
We could update the most of them (certain drivers are HD2 specific) but since we can’t update NK/SLDR sections for now you’ll got some troubles (I’ll speak of that later).
So for each package we change all files,rgu and dsm but we have to keep some modules from DFT.
For HTC_AppDrivers and HTC_OSDrivers don’t keep anything (so delete them from DFT folder) but remove HTCConnectionSetUp.dll since it is in SLDR and have some dependencies so you’ve got some troubles to connect secure wifi networks.
For HTC_8x50_OS_UI_COMMON, OEM_8x50_OS, QC_8x50_OS_GPS, QC_8x50_OS_MMRIL overwrite all modules with DFT ones
For HTC_8x50_OS_WIRELESS overwrite all modules. wl_server_serial.dll and wlan_oem.dll were files, we need updated ones in modules from new oem package for HTC Hidden Wi-Fi, the other thing to do is to verify in default.hv that BtOem, RSS and WLANOEM entries are in HKEY_LOCAL_MACHINE\Drivers\BuiltIn\ sections like in new roms and not in HKEY_LOCAL_MACHINE\Services\ like DFT’s one (and never both) otherwise it won’t work.
For OEM_8x50_OS_CAMERA replace modules and add camerasettingsmanifest.0XXX.xml from DFT in new one (since these files are normally in SLDR in new roms we have to add them). Use DSM editor to edit c6158f86-ef71-4a8b-8c04-0cf57c158b2f.dsm and add entries for these files (refer to this tool’s post to know how use it but it’s easy too).
For OEM_8x50_OS_SURF replace all modules. But you don’t have to add Backlightmdd_htc_6541.dll, just be sure you have backlightmdd.dll instead in default.hv like in new roms.
For QC_8x50_OS replace modules. You have to delete windiag.dll or verify in default.hv that “dll”=”windiag.dll” is replaced by “dll”=”” like in new roms.
6. Change OEM packages Step 3: extra packages (optional)
HTC_OEMAPPS contain OEM software.
You can add from different roms and operators. Just add the *.xap and * _License.xml you want, edit mpap_HTC_MASD_01.provxml to add/have only entries for these files and use DSM editor to edit 47c557c0-08b2-493c-a380-08c72d78e3ba.dsm and update the list of files in this package.
operatorpkg contain the HTC or Operator personalization files. Like for OEMAPPS, keep/add what you want from different roms, Email accounts/providers, Browser favorites are useful, MNS_Cust_xxx too, I’ve personally built a new theme with transparency called Aero, added the entries in the default.hv and add the 02XX*.xaml in this package.
A picture with transparency in png format for the lockscreen too.
After use DSM editor to edit 438abf0c-b691-4259-a742-1f224fa3b5ba.dsm like before.
You can add developer stuff/kitl and HTC tools packages too: AutoDeviceConfig, CommsDogfood, CoreOSDogfood, dogfoodDM, EtwChannelDefaultInternal, KitlShell, LoaderVerifierTestCerts, NetDrvVMINI, QC_8x50_OS_TEST, SensorView, SirepForPlatDev, StartKitl, TouchTools. GPSxxx from HTC_8x50_OS_WIRELESS.
Extract them from a test rom and add the content and entries in default.hv you find in rgu files.
HTC_TEST tools are xap files: DebugFlagEdit, GCFSettings, HTC BATTERY TOOL, HTCGPSTool, RegisterEdit, StopWatch, StressTool, USBModeSwitch. Refer you at the HTC_OEMAPPS explanations.
You have finished the job with OEM part, just extract the content of each of these packages in your IMGFS folder.
7. Wi-Fi problems: (optional)
Some people had some troubles with the old roms and wifi. In forum most were speaking about the SD-card but it didn’t solved the problem (and gone back to android^^).
It’s not the only problem. If you examine the file nvram.txt which is used to enable the built-in wifi chip there are some differences between files from DFT, HD2 3.14, SCHUBERT operators.
EDIT: macaddr=00:11:22:33:44:55 in its file seems the place to put a mac adress for routers with some mac filters.
I list it below, so i use a mix from HD2. When I was using the original, I didn't reached secured networks, I had to remove battery for hours.
Code:
DFT: SCH:TMOUS/WWE/TIM/O2UK HD2 3.14: SCH:Orange + MOZ:O2UK
boardrev=0x32 boardrev=0x36 boardrev=0x32 boardrev=0x36
pa0b0=5747 pa0b0=6003,6003,5576 pa0b0=6003 pa0b0=5552
pa0b1=64128 pa0b1=64086,64086,64172 pa0b1=64086 pa0b1=64245
pa0b2=65195 pa0b2=65195,65195,65155 pa0b2=65195 pa0b2=65200
pa0maxpwr=72 pa0maxpwr=82 pa0maxpwr=72 pa0maxpwr=78
opo=20 opo=16
ofdmpo=0xAAAAAAAA ofdmpo=0xAAAAAAAA
mcs2gpo0=0x6666 mcs2gpo0=0xAAAA mcs2gpo0=0x6666 mcs2gpo0=0xCCCC
mcs2gpo1=0x6666 mcs2gpo1=0xAAAA mcs2gpo1=0x6666 mcs2gpo1=0xCCCC
rssismf2g=0xa rssismf2g=0xa,0xa,0xa rssismf2g=0xa rssismf2g=0xa,0xa,0xa
rssismc2g=0xb rssismc2g=0xb,0xb,0xa rssismc2g=0xb rssismc2g=0xb,0xb,0xa
rssisav2g=0x3 rssisav2g=0x3,0x3,0x3 rssisav2g=0x3 rssisav2g=0x3,0x3,0x3
rcal_flag=0x61 rcal_flag=0x61
rxpo2g=2 rxpo2g=1 rxpo2g=2 rxpo2g=0
rxpo2gchnflg=0x1c00
btc_params6=20 btc_params6=20
I suggest to modify this entries in default.hv too
Code:
HKEY_LOCAL_MACHINE\Comm\BCMSDDHD1\Parms
"11nModeDisable"=dword:0 ; Wifi n
"PowerSaveMode"=dword:0 ; 0: Best Performance 1: Best Batterry 2: Between
"IBSSMode"="0" ; set the connection type in an ad hoc network (b/g)
"LegacyPowerCycle"=dword:0 ; new rom entry
"FrameBursting"="1" ; communication protocol (higher data transfer throughput)
8. Build your rom:
All this process can be found in the forum for more explanations:
Rename the your IMGFS folder to dump (yes you could have done it at the beginning^^) with HTCrie open the part04.bin from DFT you find in Data.zip, select IMGFS and extract IMGFS.bin
With ImgfsFromDump recompile the new IMGFS, the command line is: ImgfsFromDump imgfs.bin imgfs-out.bin
With HTCrie replace the IMGFS in part4.bin: select IMGFS, click on add files, choose imgfs-out.bin, it take only few seconds.
Replace part04.bin in Data.zip by the new one and flash it with DWI, you’ve got it!
If you like my work, don’t pay me a beer, don’t thank me but just send as much “MISS U” as you want to +33 682732382 (France)
26/06 working great for me!
No issues other than the usual bugs!
To increase the speed, download Advanced Config Tool here: http://forum.touchxperience.com/viewtopic.php?f=11&t=890 and then in the "tweaks' section, check 'Don't dehydrate apps on pause' and UNckeck 'Enable Wi-Fi 802.11n Mode' or wifi won't work. (may or may not work, try not to fiddle with the settings too much )
Mango next !!
** also reserved for future comments *** =D
oh man. what have u done!! ;-)
waiting for the link.
GOD!!!
U are the ONE!!!!
Waiting for your link...
waiting on link too.
btw what do you mean send "Miss U" to the number?
Hope this brings out others to provide custom WP7 roms.
Hi YukiXDA,
I don't think you are a "noob" by any stretch of imagination.
I must admit most of it is too intimidating for me to even think of attempting. so I will, like I'm sure a lot of other users, will be waiting patiently for you to upload the ROM.
If I understand the last part right - All I would need to do to update my phone to NoDo is flash your updated ROM using DWI, isn't it?
Not noob but I begun from scratch lol
Imagination and thinking it's possible without DFT tools and new malgr. I regret the fact that there isn't a groupware at xda to achieve such of things (and a way to update SLDR/NK) since some guys have a lot of knowledge here. I hadn't but I didn't understand and not like that we are all waiting DFT tools and release as they have it from several months. So I tried ^^
Yes I've put my Data.zip beside DWI, same way as before for now
Remeber it's a first test version, we need reports...
It's uploaded
@thebranded:
I hope It 'll encourage other people to develop more WP7 stuff on HD2 too.
The problem of updating XIP is for any phones not just ours. But new drivers for future updates yes.
"btw what do you mean send "Miss U" to the number? " -> Just send a sms with "MISS U" as text (for my private life^^)
you are a fake foreigner，bie lai zhe tao le，tao bu chu shen me dongxi chu lai de。
hi XD(XD应该是国语?)
shen ma de fu yun a
神马都是浮云，鉴定完毕！
B!ueice said:
假洋鬼子，就别来这套了，到处乱喷，没人会理你的。
Click to expand...
Click to collapse
支持B!ueice，有本事的也建個論壇搞個直刷讓全世界人看看，別只是說這不好那不好的，這顯得你很沒本事。
這到底是神馬？？跟神馬？？？
downloading now.
hey YukiXDA. what about u'r device? everything working good?
i'll test and report back.
Is this the real deal? Gotta get home & try this out. Anybody tried it yet?
Sent from my HD2 using XDA Windows Phone 7 App
JonnieLasVegas said:
Is this the real deal? Gotta get home & try this out. Anybody tried it yet?
Sent from my HD2 using XDA Windows Phone 7 App
Click to expand...
Click to collapse
Just installed now - only just got started and i don't have a code for sign in, so cant test live etc but so far looking good.
Says version is 7.0.7392.0.
Copy and paste is available and working..
wifi working...
....
It DOES appear to be unlocked - tried installing apps with toms XAP installer..
Says it fails after a while-but checked phone and app is on phone and working
this ROM
Hi,
I got an questions ?
1. How fast is this ROM ?
2. Is this ROM unlocked + prevented to lock again ?
3. Did you fix the green/yellow color after shot with flash ?
Thanks a for info and good work !
Hi all!
I want to present the tool which can port/rebuild XIP (NK) and build IMGFS partition file for Windows Phone 7 with real registry recompiling and relocations according to WP7 memory model.
It can also build NB (D000FF and WMSTORE containers) and NBH files for HTC WP7 devices (tested on HTC HD2, HTC HD7, HTC Mozart, HTC Radar, HTC Titan).
This thread is the continuation of OSBuilder for WM topic. The future discussion about WP7 ROM assembling by means of OsBuilder will take place over here
Thanks again to the team (AndrewSh, Feropont, Vladimir1973, lucifer3006) - for the support, for the tests, for your work!
Special thanks to HD2Owner for enthusiasm and his titanic work in testing WP7mode.
Thanks a lot to AnDim for his tenderness and important information provided.
Sincerely,
Barin and Ultrashot
Tutorial videos:
How to dump NBH
How to work with registry
How to work with packages.sof/packages.cif
to be continued...
[POLL] What new features do you want to have in OsBuilder future releases
Changelog links:
Changelog - OS Builder V1.4.236 FULL (01.12.2012)
Changelog - OS Builder V1.4.235 FULL (25.11.2012)
Changelog - OS Builder V1.4.234 FULL (22.11.2012)
Changelog - OS Builder V1.4.223 FULL (02.10.2012)
Changelog - OS Builder V1.4.209 FULL (19.05.2012)
Changelog - OS Builder V1.4.206 FULL (21.04.2012)
Changelog - OS Builder V1.4.205 FULL (16.04.2012)
Changelog - OS Builder V1.3.199 FULL (09.12.2011)
Changelog - OS Builder V1.3.189 FULL (08.11.2011)
Changelog - OS Builder V1.3.187 FULL (03.11.2011)
Reserved...
To -=Barin=- and Ultrashot
Dear friends!
Thank you for all the help you have given me with my WP7 experience.
I especially appreciate the information and advices you have provided, and the excellent OsBuilder you have shared with me. Your assistance has been invaluable to me!
Again, thank you so much. I greatly appreciate your generosity, willingness to help and friendship.
Regards
Andrew.
Changelog - OS Builder V1.3.187 FULL (03.11.2011)
1. Fixed issue with deleting a parameter defined in boot.rgu, if the removing directive was stored in other packages - the post http://forum.xda-developers.com/showpost.php?p=18251257&postcount=564
The second step to full WP7 support
2. Relocation engine is totally redesigned. (Hats off to Ultrashot for valuable help with WP7 modules Z .reloc sections)
3. Added possibility of porting/rebuilding XIP (NK) and the assembling IMGFS partition file for Windows Phone 7 with real registry recompiling and relocations according to WP7memory model (tested on HTC HD2, HTC HD7 and HTC Mozart. Credit for tests goes to Feropont and HD2Owner)
I want to warn that the registry files have to be checked by registry preview, because there is a hell of syntax errors in the original registry. Frankly, it seems (IMHO) that first the registry was generated and then some comments for dumb and mistakes were added.
Registry Preview will define incorrect lines to help you to fix that. The most common errors are:
- Parameter name without the quotes
- The comments are not marked with a semicolon or marked with colon.
- HEX type values end with point (the last or the only parameter line)
- The value MULTI_SZ contains comments between the lines parameter
- Existence of Directives for conditional compilation IF ... END (it's not a mistake, but currently these directives are not processed, so you should label them as a comment)
4. The dsm-editor has now the feature to set/clear Z-flags for modules.
Warning! This flag is used for WP7 XIP modules only if the RW section of a module must be located within the boundaries of RAMStart-RAMFree (nk.exe, kernel.dll, kitl_noplat.dll and similar)
5. For WP7 - Added ability to edit the file MsDefaultcerts.dat (see Additional Tools)
6. For WP7- Added ability to edit files CoreOS.dat and initobj.dat (see Additional Tools)
7. Added ability to automatically insert a certificate which will sign files while assembling DefaultCerts.dat and MsDefaultCerts.dat (for WP7) - see the settings in Build Dump and ROM. The original files stay untouched.
8. XIP Port settings - added the list of additional MS packages (for WP7). When porting WP7 XIP, the packages specified in this list will be replaced with donor packages.
At the moment, we can safely add the following packages to this list:
BaseDrivers_NK
CCFGSVC
GFX_NK
KFPCRT
Watson_Core
WinCENLS
9. In Configuration and packages tab of Setting - added the option "Always include 0409packages." If your WP7kitchen allows the language selection, it is recommended to use this option enabled to include English-language packages by default to your ROM, otherwise there is risk to get non-bootable ROM.
10. Added - the ability to build NB files (! For the moment only D000FF container !, NB assembling for the new _wmstore structure devices is not supported yet) and NBH files for WP7
To build NB you should have the original NB and should define the way to it in Build ROM settings, for example ".\NB\OS.nb". Unfortunately, to get rid of the original NB is not yet possible, but the work is in process. Hats off to AnDim for help and information provided. NBH build configuration settings are similar to the previous version, except that the CID tab can contain multiple values (each value in a separate line)
Warning! If you plan to use for cooking WP7 dump obtained by earlier versions of OSBuilder, I would strongly recommend you to dump again, and to copy the new ROM template \ ROM.tpl to your kitchen. The new template will contain additional service information, which was not recorded in earlier versions of OSBuilder
11. OSBuilder is fully backward compatible with WM6.x kitchens, (it was a big deal btw, but it was implemented). When you open the kitchen OSBuilder automatically detects the required mode WM6/WP7.
This compatibility will remain for the future, but no new features for WM kitchens will be added. OSBuilder WM Kitchens Development is terminated due to the termination of WM6.5.x development from MS side.
Thanks again to the team (AndrewSh, Feropont, Vladimir1973) - for the support, for the tests, for your work!
Special thanks to HD2Owner for enthusiasm and his titanic work in testing WP7mode.
Thanks a lot to AnDim for his tenderness and important information provided.
Sincerely,
Barin and Ultrashot
Thanks
Thank you my friends Barin and Ultrashot, with you was nice work in a friendly and well-coordinated team. Thank you for large lessons learned and tools OSBuilder.
Regards
feropont.
hd2 7720 files in the SYS and OEM Give
please
thanks
Good Job !!! keep going
yes indeed. great work barin. thanks alot.
pdaimatejam said:
hd2 7720 files in the SYS and OEM Give
please
thanks
Click to expand...
Click to collapse
just dump any mango rom to get that stuff.. what's the problem?
boot 7720 remains hd2
pdaimatejam said:
boot 7720 remains hd2
Click to expand...
Click to collapse
We do not distribute SYS here. We provide only the OsBuilder. For SYS and other device specific packages - ask in the rom topics from the rom developers.
Thanks for new version, I've dump HTC Titan rom and now trying to rebuilt.
ct_moi said:
Thanks for new version, I've dump HTC Titan rom and now trying to rebuilt.
Click to expand...
Click to collapse
Titan is the second generation device with another rom structure (_wmstore)
Only nk and imgfs partition files can be built for it, but not NB. Current version of OSBuilder supports D000FF NB container only, but not _wmstore/_wmpart
Dude you is a wonder. Thank you very much...
-=Barin=- said:
Titan is the second generation device with another rom structure (_wmstore)
Only nk and imgfs partition files can be built for it, but not NB. Current version of OSBuilder supports D000FF NB container only, but not _wmstore/_wmpart
Click to expand...
Click to collapse
Thanks Barin, that's reason why I've an error . But nice, can begin to see registry, packages etc...
Thanks a billion Barin, as well as to his team mates.
Excellent work indeed! This is what I was waiting for, before I put my hands into WP7 on HD2.
Let me dig in and see whats under wp7 hood.
Thanks again...
Best Regards
Edit:
I just tried to dump and rebuild an WP7 ROM made for HD2.
* Dumped successfully
* Fixed the registry errors
* When building, I get "The given key was not present in the dictionary." No idea what it means but I haven't changed any files/folders.
* Disable Demand Paging is empty but no idea either were does those list of modules comes while building.
Any idea whats wrong am I doing?
Great work, thanks a bunch.
CRACING said:
...Disable Demand Paging is empty but no idea either were does those list of modules comes while building...
Click to expand...
Click to collapse
Don't worry 'bout the list - it appears only because OsBuilder detects correspondent flags assigned to these modules. About the mistake - not sure -better later Barin will explain it more correctly than me....
AndrewSh said:
Don't worry 'bout the list - it appears only because OsBuilder detects correspondent flags assigned to these modules. About the mistake - not sure -better later Barin will explain it more correctly than me....
Click to expand...
Click to collapse
Ah you are right, I had forgot about DSM contains flags.
Will wait for barin reply and till then will try different ROM to see if I get same error.
Thanks...
Best Regards
CRACING said:
* Dumped successfully
* Fixed the registry errors
* When building, I get "The given key was not present in the dictionary." No idea what it means but I haven't changed any files/folders.
* Disable Demand Paging is empty but no idea either were does those list of modules comes while building.
Any idea whats wrong am I doing?
Click to expand...
Click to collapse
AndrewSh is absolutely rightt about modules with flag M in dsm
About error - no idea too. Just try to close OSbuilder and then open the kitchen again.