Related
I had a hard time to upgrade and modify my xda2 so I decided to make a small tutorial for everyone with the information’s I found on the forum. It’s not perfect but it could help.
Thank's to every one who made all this possible!!
Before starting I recommend every one to make a back-up of your rom
http://forum.xda-developers.com/viewtopic.php?t=4608
1- Extended Rom:
Your XDA2 has an Invisible Extended Rom in the device containing the operator’s configuration files and software.
Modifying it will allow you to customize the boot image and to choose the programs you wish to install during the setup of the device.
To show the extended rom on your device your need to apply this small hack and then open your file explorer:
http://www.ppcw.net/index.php?itemid=1638
2- Files contained in the Extend Rom:
Broadcast_WWE.sa.CAB:
Seems to only set the CellBroadcast setting to enabled or disabled. (I guess this refers to the Reception of News via SMS by selecting channels of interested. Quite expensive I think and only interesting for phones that do not have any other capabilities of receiving and displaying information).
T-Mobile NL sets it on, with O2 it's switched off.
CallerIDRC11_WWE_1.5.sa.CAB:
Installs the CallerID application from IA Style and the Photo Contacts extension. There are other programs that are able to provide this functionality but I use it.
CameraRC131_WWE_1.5.sa.CAB:
The camera application for taking pictures and recording videos. AFAIK there is currently no alternative to this one, you should leave it in your ROM.
GPRSMonitor_WWE.sa.CAB:
Includes the GPRS Monitor from SPB Soft. Very useful I would recommend it unless you aren't going to use GPRS anyway.
MIDI56.sa.CAB:
RingTone plugin player. Allow you to play back RingTones in the following formats: mid,3gp,mp4. Also seems to register the audio/midi MIME type for playback of midi files directly from Internet Explorer.
By default the XDA can play back only wav and wma audio files (AFAIK)
MMS1507_WWE.sa.CAB:
Installs the Arcsoft MMS application for composing and sending MMS messages.
VideoMMS.sa.CAB (not contained in Qtek):
Installs the "Video MMS.exe" file into the Windows folder. When you start it you are in camera mode immediately and after you have recorded a picture or video you get into MMS composition mode.
This seems to be just an easier way to compose MMS messages since the main MMS Application (see above) is already able to compose MMS messages.
OEM_AKU1_WWE_4AP.sa.CAB (named OEM_4AP_WWE.CAB in Qtek ROM)
Installs the following files: GPRSAuthentication.exe, BTSetting.exe, STK.exe and WModem.exe
I am not sure if these are customized versions or if the normal ROM doesn't contain them. Well perhaps not because these are specific to the Phone edition so they can't be present in the main ROM, maybe they are contained in the Radio ROM, but probably they are only contained here, meaning you shouldn't remove this cab file.
OEM_WWE_03120301.sa.CAB (named OEM_WWE_03122301.sa.CAB in Qtek ROM)
Installs files for Bluetooth: AudioGW.dll, BthASPlugIn.dll, rilgsm.dll, Serial3.dll and Wavedev.dll. Also contains the new feature of mapping a (dynamic) serial port for BT.
I think you should not remove it.
TM_phone_class10.CAB (not contained in Qtek):
Installs several registry settings regarding phone functionality. (See my other post regarding this topic: http://forum.xda-developers.com/viewtopic.php?t=5539)
TMCOMREG.sa.CAB (not contained in Qtek):
Contains some of the settings contained in the previous one anyway. I'm not sure if it does anything else but I don't think so.
TMD_AP_NL.sa.CAB (not contained in Qtek):
Implements several settings specific to T-Mobile (NL): Restricts video types for MMS. Adds connection and gateway settings for MMS connection via T-Mobile NL. Adds a T-Mobile profile to GPRS Monitor.
I would not install this cab unless you live in NL!
TMD_NL.sa.CAB (not contained in Qtek):
Sets the HKEY_LOCAL_MACHINE\SOFTWARE\OEM\3rdversion\MSYSTEM1 value to the provider name.
Not required!
TMDNLCustomize.sa.CAB (not contained in Qtek):
Adjusts all the "theming" stuff: Changes colors, installs Today-theme, installs T-Mobile Dialpad, sets T-Mobile ringtone.
If you don't like you xda2 look like a pink pig you should leave this out.
(You can extract single items from the cab file if you like)
t-mobile_shortcuts_only(UK).PPC2002_ARM.CAB (not contained in Qtek):
Contains some strange things that seem to me rather useless: "WebDisplayText t-zones", "T-Mobile Resetter.exe", "T-Mobile PIE Launcher.exe", "TMobileWebToday.dll", "T-Mobile Homepage Plugin".
I wouldn't install this one!
Version_AKU1.sa.CAB (Version_AKU1_160.sa.CAB in Qtek):
Seems to only set the version number of the extended ROM in the registry.
3- Modifying and editing your Extended Rom:
Most of the latest XDA2 have a write protected Extended Rom
A) For NOT Write Protected Extended Rom:
If your XDA2 Extended Rom is not write protected just add the new files you want, you can find on the forum many different extend rom files (O2, T_Mobile, Orange) and kitchen your own extended Rom by adding the cab files directly in the Extended_rom directory and soft reset.
B) For Write Protected Extended Rom:
The only way for the moment (until we find a way to make the rom writable) is to use the upgrade programs used by the operators and ER2003Edit program.
1)- Download
http://www.c1au.com/iMatePDAROMS/ruu15283.zip
or
http://www.clubimate.com/Support/ruu113sku1.zip
2) Simply unpack the complete T-Mobile Rom update file (it's a zipped EXE) into a folder.
There you will find these 6 files:
- HimaClearJumpCode.exe
- HimaGetDeviceData.exe
- HimaUpgradeUt.exe
- ms_.nbf <----- this is the file which holds Ext Rom!
- NK.nbf (main rom)
- Radio_.nbf (radio rom)
3) Delete the other *.nbf files to prevent updating the full XDA2/MDA2 rom. You only need "ms_.nbf" and the "*.exe" files!
4) Now modify the ms_.nbf with the tool softworkz kindly provided.
http://wiki.xda-developers.com/wiki/ER2003Edit
5) After this, install the modified ext-rom to your XDA2/MDA2 by starting "HimaUpgradeUt.exe" and follow the instructions!
6) If you get a country code error during the install you will need to modify the country code included in the ms_.nbf file
- Download xda2nbftool
http://forum.xda-developers.com/viewtopic.php?t=5563
- Put xda2nbftool.exe in the same folder as your ms_.nbf file
- Run xda2nbftool.exe from Command Prompt and type the following command
xda2nbftool.exe -so O2 -v ms_.nbf
Replace O2 by your operator’s name (ex: orange, O2 etc)
It should now work!
cheers,
Yann
nice one Yann
Thanks
I had a go at doing the "if your extended rom is protected"
I down loaded the file
1)- Download
http://www.c1au.com/iMatePDAROMS/ruu15283.zip
and accidentally ran it.... I know I was stupid... I now have an I-Mate instead of a XDA - O2. Please help can I get the O2 back is there a programme that does the same as the one I just have used. It has changed every thing the radio stack, the other bits of software, I am just pleased it still works of calls.
I couldn’t find the indivuiual HimaUpgradeUt.exe programme any ware.
Please help I am really stuck at the minute!!
The bit I didn’t understand was the bit about unpack the exe. Which I now understand how to do. Although I have upgraded to Rom 1.52.00wwe, radio version 1.06.01, I can haply say I have the original O2 rom back in place with additional programmes installed in the Ex-Rom. I had a fair bit of space so I popped some music files in as well!!!!
Thanks for all the help!!!!
thanks yann for the perfect summary
as newby i needed something clear like this to dare my first rom changes, and i successfully did!
it would be even more perfect if also somehow the program settings/passwords could be cooked in/restored from the extended rom. i searched the forum but could not find any hints.
Are there methods for this ?
Perhaps a silly question, but I'm fairly conservative when it comes to messing around with my device.
How do you find out or know if your Ext ROM is write protected or not? I know that I can add applications to my Ext ROM and it does not seem like I should be able to do that if it's write protected, but then again I'm not sure if this matters.
Ed
ed, if you can copy files to your ext-rom via activesync, it is per definition not write-protected.
your not that conservative, because you already run a tool or edited the registry to be able to see the ext-rom
ronald,
Well I guess you are right I do like to play around, as I get more comfortable doing so. It is this Forum, guys like you, and some other forums that have made this possible for me to do. For some reason I'm more comfortable in general hacking around a desktop pc than a PPC.
I thought my Ext ROM must not be write protected. When I deleted the TMD files, described here as useless, I got the message that they were read only, but they did go away from the Ext ROM Folder. I do not notice a big difference, however, nor did it free up that much memory. I was thinking that I might need to do more then this. Do I?
So basically, if my Ext ROM is not right protected, and I have been already loading programs into the Ext ROM, I’m pretty much at the place people are trying to get with the Ext ROM Cook ER...Edit. Is that correct or am I missing something here?
Ed
Ed,
I do not like flashing rom (or bios) on either my desktop or PDA (if not absolute sure to fix bugs). However flashing the PDA's ext-rom can basically not screw up the PDA because you don't touch the OS, so I flashed the ext-rom to get familiar with the PDA flashing in general (and also to have a restore of my standard used software after a hard-reset).
About your ext-rom; I do not recognise your situation. I would say if it is read-only the file will not disappear (like with my PDA).
I did notice while editing the ext-rom file for flashing that the file is fixed ~16MB, regardless of which cab's are included or deleted.
Maybe this is the same effect that you see when deleting the file in the ext-rom ???????? (although I can imagine both effects have no relation)
ronald
Camera Programs
Okay,
I made a custom ROM with the following programs:
CAB: \Extended_ROM\CameraRC131_WWE_1.5.sa.CAB
CAB: \Extended_ROM\CallerIDRC11_WWE_1.5.sa.CAB
CAB: \Extended_ROM\MMS1507_WWE.sa.CAB
CAB: \Extended_ROM\GPRSMonitor_WWE.sa.CAB
CAB: \Extended_ROM\Version_AKU1.sa.CAB
CAB: \Extended_ROM\OEM_AKU1_WWE_4AP.sa.CAB
CAB: \Extended_ROM\OEM_WWE_03120301.sa.CAB
CAB: \Extended_ROM\VideoMMS.sa.CAB
Awesome, alot less bloat, but.... Camera doesn't work.. Application says Camera is not a valid Pocket PC application. :: grumble ::
Did I miss something?? Camera.exe is there, but doesn't work
Brandon
My Ext ROM is not write protected, and I'm able to run applications in the EXT ROM Folder. I deleted the 2 TMD and the T-Mobile cab files, but I have not nticed a big difference, nor is my GPRS back to always on, which it should be now.
Perhaps the device requires another hard reset without these cab files in place prior to the changes taking actual effect. Does anyone know if my assumption is accurate about the required hard reset?
Ed
what dictates if the ExtROM is write protected or not? is it the version? or the hardware itself? or a mix of the version with the OS checks?
cuz i believe the ROM version is dictated by the version_AKU1.sa.cab. does that mean we can hack the cab (or use a diff version) to disable the write protection?
i'm using a himalaya btw.
I have a question or two.
I'd also like to know if it is possible to modify CAB files so they install an application and then also put in your purchased key or serial depending on the application so it's already registered to yourself. It seems like it must be possible because the GPRS Monitor on the T-Mobile Extended ROM is already Registered when you try and register it yet I was under the impression it normally has to have a key entered to turn it into the full version with no limits.
This would be great if this was possible, if it's a key file then it's simple to copy it over but how about automatic registry entries? Are these done similar to Windows .reg files? Does anyone have any info if a .reg file can be make and run from the Extended ROM to make changes to the registry? This would also allow me to key in a few other things I'd like presetup.
Is there a way to see what registry changes a CAB file makes other than from purchasing MagicCAB? Is there a free program like this? It seems like a reasonable program from the info but I don't want to spend 10 dollars on a program I might only use once or twice.
Acutally, one more while I'm here. Does anyone have a CAB installation version of CabInstl which puts a shortcut in the Programs or an easy way for me to make that? I've set it up so it will copy the EXE in manually along with a shortcut but I've yet to try it. I think it should work OK I imagine, just might be neater and have an uninstall if it's in a CAB format?
Can you delete files from the extended ROM script? Just so I can clear out a few folders of things I don't want in there when I do a hard reset?
Thanks for all your help. I'm looking forward to making a super kick ass Extended ROM for myself, I'm half way there
Updating the indirect way
Had a few problems with the updating process... and thought i would explain how I got around them!
First I updated to the standard 16007DE ROM
Then I installed the Extended Rom Viewer, and then because it is protected, i copied the contents to my HDD.
Then i tried to open the Rom update from T-mobile with the Extended ROM editor, but kept on getting file access errors The only one i could open was the NL 13006 version. So I changed the splash screen, deleted the origianl contents, and then inserted the contents from my updated original Extended ROM, as well as a few other bits that i could find, IE the extended ROM viewer. It is updating at the moment, So I hope it all works.
I have a few questions though!
Does anyone know a way in which I can automatically install a few themes, and a few ringtones? I have a few MIDI files that i want to be installed into the windows\rings folder, and the themes need to go in a folder called themes in My Documents. I also wanted to ask if there is a way to extract the CAB from another program, for instance Voice Commander. It is an MSI, but only works in windows!!!
Any help would be greatly appreciated...
Greets from Hannover, Germany
Juggs :?
Is this going to work:
- Download ER2003Edit
- Download the O2 XDA2 ROM 1.60.50
- Download the T-Mobile MDA2 ROM 1.60.36
- Remove O2 apps i don't want to use
- Add applications from T-mobile rom which i want to use
- Change ROM provider from O2 rom to to T-Mobile
- Save new O2 ROM and upgrade
But... I want to add custom ring tones to contacts, and if possible also want to add custom picture. Also my camera must be able to work. Which software do i need for this?
Because.. All i want to upgrade is today theme to O2's and also the software to 1.60.50... Does the O2 rom also has an "TMDNLCustomize.sa.CAB" ?
Greek full support language for qtek 2020
Hello,
this is a very intresting site!
Can anyone tell me is exist & where can i dinf an extended rom for qtek 2020 with full support of greek language?
Also there any newer version than the 1.66.00 wwe extended1.66.130 radio 1.10.00 wihich my qtek 2020 has??
best regards
george
A) For NOT Write Protected Extended Rom:
If your XDA2 Extended Rom is not write protected just add the new files you want, you can find on the forum many different extend rom files (O2, T_Mobile, Orange) and kitchen your own extended Rom by adding the cab files directly in the Extended_rom directory and soft reset.
B) For Write Protected Extended Rom:
The only way for the moment (until we find a way to make the rom writable) is to use the upgrade programs used by the operators and ER2003Edit program.
Click to expand...
Click to collapse
2 questions for you,
1. how do i know whether my rom is the editable 1 or the non editable one?
2. I tried option A, just mergly adding the CAB files into the EXTROM but... when the hard reset was perform it did not install the CAB files i added in? what could be the prob i know there is a "autorun.exe" in it but i dunno whether will it affect the process. I also notice a "config.txt" in the extrom, tried editing it but it seems that nothing happen
Reason for adding the cab files is because i was using a 1.72.00 rom with radio stack 1.12 but intend to change it to radio stack 1.14 and also try cooking up my own rom in the ktchen but after doin so its like nothing happen. need some advice for cooking roms in the kitchen been searching the forum... found a few but its all talking about Linux platform.
Hi Kelvin,
1)
The way to know if your rom is not writ protected is if you see a folder called extended_rom in the root of XDAII and if you can add files in it.
If not, there’s a nice tool to make the extended_rom visible and to make it writable.
http://forum.xda-developers.com/viewtopic.php?t=8422&highlight=extended+rom+hide
2) The config.txt is made to lunch the programs in the extended rom when you hard reset the XDA or when it starts for the first time.
You just need to put the cab files in your extended_rom folder and edit the config.txt this way:
Exemple:
I added the cab file vxIPConfig.ppc3_arm.CAB in the folder extended_rom
and added this line in config.txt
CAB: \Extended_ROM\vxIPConfig.ppc3_arm.CAB
Cheers,
Yann
hi yann,
i tried doing that way as i figured out that config is like a startup "prg" to actually start the programs installing when hard reset is performed. But the thing is i cannot make the programs i added in the install after the hard reset is perform. I don't know why but the rest of the cab files can be done. Do adding of all this cab files into the ROM consider cooking ROM??? not really fimilar with the terms of cooking ROM unless that is the way.
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
Since i'm not going to cook just yet for the Pro, nor am i helping out any specific crew Over At the Pro (SPC crew will come over to Pro someday anyway).
I have decided to make a OEMMORT Packages Repository.
For those that want to cook with the utmost optimized packages for their Pro.
OEM PACKS
To use these Optimized Packages to Cook (specifically with Touch Pro In Mind), you always need the the MortScript Base.
So if you use more or less packages the RFO.mscr & CLASC.mscr need to be adjusted appropriately to correspond with the correct File Operations.
Mort Script 4.112.b7
AdobePDF_2_5_103401_01
IA_ZIP_1_21_18171328_1
More coming eventually.
Explanations
If you do see the Logic and and improvements this adds to cooking control and performance enhancement, then don't forget to mention the SPC-MORT-COOKING Style, Wax in Wax Out
Any Comments, Opinions, Ideas or Questions welcome.
TNX to the rest of the bengalih for some pointers & SPC crew for testing and helping out.
And thanx of course to MORT.
Don't Know MortScript? Shame on you. (neither do i)
Donny Bahama's easy to carry Mortscript Manual in HTML:
http://forum.xda-developers.com/atta...9&d=1214102654
excellent stuff
Hi Noonski... Very interesting concept.. Great Works! Cheerz..
would it be possible to put the cab files from UC all into 1 zip file to save space ?
da_jojo said:
would it be possible to put the cab files from UC all into 1 zip file to save space ?
Click to expand...
Click to collapse
ExactMundo.
If you'd make the cab files into OEM packages first.
I have a WNDWS.zip
PRGF.ZIP
and a MYDOCS.zip
But even that would not be needed as one zip file should be able to do it.
As long as the Makedir command is used in a Mortscript before the Zip is extracted for folders that do not exist unless you have the complete folder structure in the zip files.
Unless you mean the Cabs from the UC on your SD card.
But even then you could also only extract just a cab at a time.
So i'm not sure you meant the ROM Autorun Cabs or the SD UC cabs?
Also unzipping the files instead of having them in Rom, or making the links with a script removes that darned ROM Read File Protection.
yes yes yes that is what i mean exactly my friend
i mean both ... it would save space on the storagecard as well as remove this freaking writeprotect on the dirs. dir structure in the zip file would be the best option i think as it copies 1 on 1 without setting userrights.
this writeprotect option is set on a hidden part of the systemflashdrive. in the mft i think. strange thing is that i got acces to my windows folder through activesync and it doesnt work on vista mobile device center.. frankly i have no idea what i did but it seems something in the pc as it works on my xp machine and not on vista. i didnt change anything yet on the phone itself relating to this.
pocketcommander www.totalcommander.com is able to ignore or overwrite the writeprotected files in windows dir so there must be a sollution to this.
i dont have the proper tools to do all this stuff but it would be the fastest way to extract all files from all cabs one need into one zip file and let mortscript handle the unpacking and settings of the registry. this way theres no need for autorun cabs merely the UC SD installer. maybe someone can make an nice logo for the custom uc installer.
da_jojo said:
yes yes yes that is what i mean exactly my friend
i mean both ... it would save space on the storagecard as well as remove this freaking writeprotect on the dirs. dir structure in the zip file would be the best option i think as it copies 1 on 1 without setting userrights.
this writeprotect option is set on a hidden part of the systemflashdrive. in the mft i think. strange thing is that i got acces to my windows folder through activesync and it doesnt work on vista mobile device center.. frankly i have no idea what i did but it seems something in the pc as it works on my xp machine and not on vista. i didnt change anything yet on the phone itself relating to this.
pocketcommander www.totalcommander.com is able to ignore or overwrite the writeprotected files in windows dir so there must be a sollution to this.
i dont have the proper tools to do all this stuff but it would be the fastest way to extract all files from all cabs one need into one zip file and let mortscript handle the unpacking and settings of the registry. this way theres no need for autorun cabs merely the UC SD installer. maybe someone can make an nice logo for the custom uc installer.
Click to expand...
Click to collapse
I think for that for the SD Autorun UC solutions there are already a few good solutions around some even supporting Mortscript.
And they all are pretty user friendly to.
Depending on what a user wants and knows, using mortscript being cooked in just gives them more freedom to play around customizing a cooked rom.
But it would need more hand work using your method, but it is possible of course.
It boils down to, do you like making Mortscripts to change registry settings or do you prefer making PROVXML files?
And not everyone is into decompiling cab files to make them fit their exact requirements.
But there's only one rule, Copy the Script to device memory and a folder name tat does not contain a space in it's path. And then run the script.
As the Exec: command from autorun doesn't like that.
But mostly the main way i use it is for the Cooked Autorun part.
I control when the Welcome wizard is run, Before Autorun or after the boot.
I can remove the extra parts of the Networkwizardauto.exe files and also run the networkwizard when i want during the process.
All i need to ad to my process is to open the Locale Preferences dialog during this process and then finish it of with Syncrotime. (or asking for the choice if you want threaded SMS on or not, the possibilities are plenty)
Put all the Setting up your device options after each other for those users that don't have the know how of how to use UC to setup their personal settings.
I even delete the back up files for the one App that i only get installed correctly through a cab file
DelTree( "\Windows\AppMgr\SRS Labs SRS WOW HD" )
So i hope that those that cook or customize and want even more control and detail into what happens can appreciate this.
I know i'll keep using this, and adjusting all my OEM packages to it. Because i have experienced the overall speed improvements in the Rom because of it.
I'm not a Pro in Mortscript and myself i only use the fairly simple commands.
i see.. thnx for explaning
it would be far simpeler using the xmlprov
unless one requires the extra functionality of mort script
the SRS wow HD is a driver enhancement so it needs the system to detach the driver which is only possible with the installer . hence cab files work good cause the're installed by the windowsinstaller which can temp disable the driver.
Instead of MortScript, there is a Yonsm's CeleCmd that perform roughly the same thing.
Check it out!
http://www.yonsm.net/read.php?329
V
vibranze said:
Instead of MortScript, there is a Yonsm's CeleCmd that perform roughly the same thing.
Check it out!
http://www.yonsm.net/read.php?329
V
Click to expand...
Click to collapse
Hey Vibranze, Long time no See.
Would you mind translating
Mort has a bigger fanbase here on XDA.
Yeah, long time no see How are you?
I really not used to your new avatar, without the cigarette it's not like you at all hehe
Actually you can try to download it and check out the sample, it's very easy to understand. I attached here for you
Anyway, here is the translated page by Google.
V
Noonski said:
Hey Vibranze, Long time no See.
Would you mind translating
Mort has a bigger fanbase here on XDA.
Click to expand...
Click to collapse
Explanations
What Does RFO.mscr do?
What Does CLASC.mscr do?
Which Packages Contain Modules and Why?
There's Files Missing from the Packages?
What Does RFO.mscr Do?
Well this script is copied to the regular Start up Folder in Windows.
I use short file names because as much as possible for anything that goes into Windows folder and have no other use being in the Windows folder then being copied by initflashfiles to another folder.
RFO.mscr basicly is the only file i use an initflasfiles.txt for (goes to \Windows\StartUp\ReplaceFileOperations.mscr)
Because after that it takes over the File Operations of the Default build in initflashfiles method.
Why?
Well You don't need actual shortcut files present in ROM to make them.
Code:
CreateShortcut("\Windows\StartUpDisabled\btdwake.lnk","\Windows\btdwake.exe")
in the RFO i don't put that much actual File Operations.
Only the ones that might be useful.
(Why start up WiFiInit.exe during autorun, if it's only useful after the Autorun reBoot?)
Code:
CreateShortcut("\Windows\StartUp\WiFiInit.lnk","\Windows\WiFiInit.exe")
I basicly set up the Second mortscript that will run after the Autorun reboot.
And i make sure the script is not to short. A script that is to short might actually copy the second script so fast into the autorun folder that it will actually be run immediately at during Autorun.
And i make sure the script deletes itself
Code:
RegDeleteKey( "HKLM" , "Services\SqmUpload" , TRUE , TRUE )
RegDelete( "HKLM" , "init" , "Launch99" )
SetFileAttribute("\Windows\StartUp\ReplaceFileOperations.mscr", "readonly", FALSE)
SetFileAttribute("\Windows\StartUp\ReplaceFileOperations.mscr", "system", FALSE)
CreateShortcut("\Windows\StartUp\WiFiInit.lnk","\Windows\WiFiInit.exe")
Copy( "\Windows\CLASC.mscr", "\Windows\StartUp\Clean AutoShortCutStartUp.mscr" )
Delete( "\Windows\StartUp\ReplaceFileOperations.mscr" )
So you can choose during which Boot you want to do what.
But it's better to do it after the first Reboot in case there is no Autorun installation and the phone reboots before finishing the RFO script.
So the Yummy goes to the CLASC.mscr.
What Does CLASC.mscr Do?
Well this does the actuall JuJu...
It takes over the Job of AutoAttribute.exe, so that can be kicked out of the Rom.
Code:
SetFileAttribute("\Windows\StartUp\Clean AutoShortCutStartUp.mscr", "readonly", FALSE)
SetFileAttribute("\Windows\StartUp\Clean AutoShortCutStartUp.mscr", "system", FALSE)
It Takes over the Job of AutoShortcut.exe and initflashfiles.
(less autoshortcut.provxml files in the final rom for the people to lazy to put these into a .rgu file for correct cleanliness)
Also Autoshortcut.exe is set up to run and check the regsitry at every Boot up, so out with this nonsense.
Code:
MkDir("\Windows\Start Menu\Programs\Office")
CreateShortcut("\Windows\Start Menu\Programs\Office\Adobe Reader.lnk","\Windows\AdobeReaderLE.exe")
And eventually it run some Post Stuff to make setting up the device easier at first boot.
Code:
Run("\Windows\ConnectionSetup.exe")
Delete( "\Windows\StartUp\Clean AutoShortCutStartUp.mscr" )
Message("Thank you for installing A SPC Optimized Rom. ","Installation Finished")
Also sometimes people encounter a registry setting that does not get applied directly because of .rgu or .provxml conflict.
So instead of making a new EXTRA .provxml file to fix this.
The registry setting can be added to a file that is already there.
Code:
RegWriteString ("HKLM", "Software\Microsoft\MediaPlayer\Skins", "DefaultPortraitSkin", "\Storage Card\My Documents\Windows Media Skins\Mono SPC\portrait-htc-touch.skn")
RegWriteString ("HKLM", "Software\Microsoft\MediaPlayer\Skins", "DefaultLandscapeSkin", "\Storage Card\My Documents\Windows Media Skins\Mono SPC\landscape-htc-touch.skn")
Or create a new start up script that runs at every start up when you have these annoying Registry settings that for some reason like to reset to a specific default value.
Code:
WriteFile("\Windows\StartUp\FixRightSFTKey.mscr", 'RegWriteString("HKCU", "Software\Microsoft\Today\Keys\113", "Open", "\Windows\Submenus\Contacts.mbi")^NL^RegWriteString("HKCU", "Software\Microsoft\Today\Keys\113", "Default", "Contacts")')
Less headaches going trough all the files finding the conflicts, as you now have a sure fire hit to get the registry right.
And we all know that eventually you will stumble upon the rgu or provxml file that is causing Havoc. But at least you don't have to stay awake pounding your head to find them.
Which Packages Contain Modules and Why?
Well the ones that do have Modules instead of regular files most propalby..
Work as a Module.
Show improved starting up of the application
Can be made into a module to start with (not all files like this)
Show improved handling speed or usage performance.
So when you do find Modulated files in the packages, these have been tested and found worth modulating.
These days most of the kitchen's have G'Reloc.exe build into the cooking process.
So the chance of Modules overlapping a specific memory allocation/space is fixed.
Some kitchens also offer this functionality to Make Modules of files.
But in some Junior Cheffs cases, that usually will result in (nice term coming) OverModulating.
If the kitchen you are using does not run G'Reloc.exe automatically please do so manually when cooking packages with modules.
I have tried making some OEMs myself from Cabs (with some success).
I was wondering 2 things.
Does anyone know of anywhere that OEMs are downloadable. I am looking for programs like:
S2P
S2V
S2U2
TouchFlo
iContact
LiveSearch
Opera Mini
Mortscript
Weather Panel
Today Agenda
UL
I am thinking that my problems stem from the final stage
"The next window that appears, known as the 'initflashfiles tab' is for executable and help file links. Select which files you want your links and the folders to place them. Select and apply for each link and when finished, click done to proceed."
Can anyone explain this a little clearer? Do I actually have to do anything in this screen? I would love to be able to cook my own ROMS to make it easier to get my phone where I want it after a hard reset.
Also does anyone know if you can alter the OEMs and cook them. For example, could I replace the default themes in Weather Panel with the Diamond ones so that I do not have to copy from the card when resetting?
Sorry for all the questions but I recently did my first flash and now have the bug and it takes me ages to install everything every time i do it.
I get all mines from ppcgeeks some work with dcd some don't.
I use the UC option in the kitchen and use the OEMizer to create the info for it to install the CABs you want. They must be on your SD Card but it works great. It will also copy files from the SD Card to Main Memory as well. It is supposed to be able to make registry changes to but I never got that to work with just editing the provisional.xml file. OEMizer is great for several settings any ways and you will have your own personal OEM to put in the kitchen to bake.
PPC GEEKS oem.rar for the easy out way or if you are into learnning any of it oemizer works pretty good to.
I have use some on this post.
He does take request.
http://forum.ppcgeeks.com/showthread.php?t=25696
Wow, thanks for that last one, I will post some of my requests on there as well. Can't wait to get cooking!
Here are some I have made......
Update 2009/04/12
Here is a working cab to enable "Rogers/Fido Call Display" by Captain_Throwback. This cab has been tested and proven to work with many ROMs. I've personally tested it on "Energy" and "RoMEOs" ROMs and it work like a miracle. A big bravo to you, Captain
----------------------------------------------------------------------------
The QUICK/EASY method on Post #14 only work for ELITE RC2 (cab file included)
----------ROMs that work for Raphael----------
NATF's v4
Lantis OS 21009 AKU 1.5.0 v3.00
RRE Canadian 4.1
PROven ROM 1.12
Elite RC3 will include this option
For Da_G ROM and Shipped ROM, you simply have to replace the dll file
----------This is how you do it, for chefs----------
After 33 hours straight non-sleep, and plenty of pm to Da_G and NATF, I can proudly say that we've found the perfect answer for this problem
and finally we can put an end to this question "how to make Rogers/Fido Call display to work?"
I've tested this and believe that this solutions may work for any ROM. So far I've tested with 2 of NATF's ROMs, but I need someone to test
this on Kaiser and other device as well. You don't need to used a Shipped ROM, but you can apply these step to any of your favorite ROM.
2 simple steps in summary:
First you need to cook rilphone.dll file into your ROM in the folder /OEM/OEMDrivers/
Second, you need to change the file that setup all the registry key to your device when you flash
For Fuze (may be different for Kaiser), this is the file: /OEM/OEMDrivers/de3f3189-9f71-4162-9f26-39393dcc8c94.rgu
(I attach the original file from Da_G's clean ROM)You can either just replace this file or simply go in the file and Make
sure that all lines related to these regs are the same as the one I've posted here (took from Da_G's ROM)
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL]
[HKEY_LOCAL_MACHINE\Software\Microsoft\RIL]
POST #12 includes all registry lines that I've modified
The Files are attached.
----------How to cook rilphone.dll into your favorite ROM, from Da_G's words----------
Code:
[B][COLOR="Indigo"]-=01=-[/COLOR][/B] Download a ROM Kitchen for your device, for Fuze is RaphaelKitchen
[B][COLOR="Indigo"]-=02=-[/COLOR][/B] Extract Kitchen
[B][COLOR="Indigo"]-=03=-[/COLOR][/B] Copy your favorite ROM *.nbh file into \BaseROM\ folder (from extracted Kitchen)
[B][COLOR="Indigo"]-=04=-[/COLOR][/B] Rename your *.nbh file to RUU_Signed.nbh
[B][COLOR="Indigo"]-=05=-[/COLOR][/B] Launch "RaphaelKitchen.CMD" from *Kitchen\ folder
[B][COLOR="Indigo"]-=06=-[/COLOR][/B] choose "e" for extract, then "a" for from BaseROM "RUU_Signed.nbh
(if everything work so far, your dos should be running on it own now)
[B][COLOR="Indigo"]-=07=-[/COLOR][/B] When it's done, check if you have these three main Folders
+/OEM
+/SYS
+/ROM
(make sure they are not empty or only have 1 sub folder. if this is the case,
then your favorite ROM is protected... ask the cook nicely to share with you
those 3 folders)
[B][COLOR="Indigo"]-=08=-[/COLOR][/B] replace these 3 files into /OEM/OEMDrivers/
[URL="http://forum.xda-developers.com/attachment.php?attachmentid=141542&d=1230689478"]+"rilphone.dll[/URL]",
[URL="http://forum.xda-developers.com/attachment.php?attachmentid=141541&d=1230689478"]+"de3f3189-9f71-4162-9f26-39393dcc8c94.rgu"
+"de3f3189-9f71-4162-9f26-39393dcc8c94.dsm"[/URL]
[COLOR="Red"][B][SIZE="2"]It's recommended that you modify the *.rgu file instead of replacing it for a moded ROM,
because of all the tweaks chefs have added.)
For list of registries that I've changed in the *.rgu file, [URL="http://forum.xda-developers.com/showpost.php?p=3106249&postcount=12"]READ POST #12[/URL][/SIZE][/B][/COLOR]
[B][COLOR="Indigo"]-=09=-[/COLOR][/B] Launch "RaphaelKitchen.CMD" from *Kitchen\ folder again
[B][COLOR="Indigo"]-=10=-[/COLOR][/B] chose "cf" for cook and flash a ROM, then "b" for "if you want to use the
new BuildOS+Package..."
[B][COLOR="Indigo"]-=11=-[/COLOR][/B] Ervius Package _tool+BuildOS windows will launch, choose "BuilOS" tab
[B][COLOR="Indigo"]-=12=-[/COLOR][/B] click on "Load ROM", now choose your Kitchen/ Folder where you have
OEM/ROM/SYS folder, then click ok
[B][COLOR="Indigo"]-=13=-[/COLOR][/B] Click on RUN, once it finished loading the ROM. When you see the
word "Done" Close Ervius by clicking on the "X" button
(your DOS will run again, and ask you to press any key to start... Press
the "any key" :p )
[B][COLOR="Indigo"]-=14=-[/COLOR][/B] While it's running, it will open a tables with a bunch of numbers that
you don't understand
(it's checking the memory)... just close it by clicking on the "x" button.
(your Dos will run again, till you get your favorite Flash Window come up...
from here, you're on your own)
Don't forget to HardSPL your device before FLashing your device.
Let us know if this method work for you.
I'm also inviting all the Chefs to join the fun and provide us a Canadian version.
----------Credits----------
This tweak isn't perfect, but took me a while to make Rogers/Fido Display work. However I wouldn't be able to get this far without the helps of Da_G, NATF, trueg and a bunch of other people that I've bugged.
At least give some credits to those who have spent so much time to make this finally happened. Like Da_G said, a donation isn't required, but always appreciated.
Donate
Also, thank nitroblu and y2whisper and other Canadian users who has tested and post their results
There were many bounty offering for this discovery, but none of them keep their words... so disappointed... anyway
----------Found issues----------
1- Does not work while MSVC phone notification is activate.
2- May have issues with QuickGPS (not yet confirmed)
3- It froze my device every-time I run it with spb Wireless (need confirmation)
Can any Mod Change the topic of this one to "[Tut]First step to Canadian ROM, Rogers/Fido Display on your Fuze"
Click edit on the first post, then click advanced edit, you can change the topic from there
Da_G said:
Click edit on the first post, then click advanced edit, you can change the topic from there
Click to expand...
Click to collapse
Thank you... Now, I'll leave the Rom Cooking to the real Chef... I'm going to bed
so happy now
Hi pandaboyy,
Thanks for doing all the hard work. I am in Toronto and use Rogers and ever since I got my Tilt2 earlier this year I have been missing the name display. I just got my Fuze from the states today and installed NATF v3.2 rom. I look forward to having name display working again.
Just one question: any way to put this in a cab or build it into NAFT roms?
Thanks again.
Rob.
talonrob said:
Hi pandaboyy,
Thanks for doing all the hard work. I am in Toronto and use Rogers and ever since I got my Tilt2 earlier this year I have been missing the name display. I just got my Fuze from the states today and installed NATF v3.2 rom. I look forward to having name display working again.
Just one question: any way to put this in a cab or build it into NAFT roms?
Thanks again.
Rob.
Click to expand...
Click to collapse
Hey Rob,
I was about going to TO today to celebrate New Year Eve, but since I didn't sleep I got lazy out and drop the plan (true story). I don't think a cab would do the job. Da_G did explain it, but trust me, I still don't understand why
Da_G said:
Yes, the reason my method does not work is because the rilphone.dll is not signed with a trusted certificate as I stated..
Click to expand...
Click to collapse
And since I'm far from a chef, I really don't know how to cook a cab sorry.
However, try the cooking process that I mentioned in the first post. It's as easy as 1-2-3 and it's fun to start understand a little bit how your device work. Once you open the "de3f3189-9f71-4162-9f26-39393dcc8c94.rgu" file, you'll see that's the whole reg setting of your device. This may helps in the future, because you can actually customize your ROM so that whenever you re-flash it, your reg is already added.
Just try the Kitchen_Raphael (it's small and very easy). It'll take you about 15min to do the whole thing... with NAFT's permission, I'll try to release v3.2 with Rogers display. However, here is a good news for you; NATF is trying to release the first Canadian ROM very soon
Help me to Help you
I was trying change the entry in de3f3189-9f71-4162-9f26-39393dcc8c94.rgu file instead of replacing it to keep all the Tweaks that NATF has done. However, I come up with this error when I tried to build the ROM
"Error building default.hv and user.hv! (see "BuildOS-log.TXT")
I take a look at the file again, and I don't see any important different except for the file properties (ignore the size). Look at the image. The working file is hidden and the hidden option is disable. The non-working file is hidden, but not disable
how do I change make the file hidden and disable the option? I know that DOS can do it, but I just don't know the command.
EDIT---------------------- Solved the problem, but still want to know how to disable Hidden option-----------------------
Ok, I've read several post around the forum, and quite honestly, it didn't help much.
so I did a trial and error... If you want to edit your the de3f3189-9f71-4162-9f26-39393dcc8c94.rgu instead of replacing it, Don't overwrite the file.
1- After you finish to edit save it with another name eg: de3f3189-9f71-4162-9f26-39393dcc8c94_test.rgu.
2- Delete the original file (or move it somewhere else to be sure)
3- Rename your test file to the original name: de3f3189-9f71-4162-9f26-39393dcc8c94.rgu
4- Right click on the file, Properties then make it Hidden
(You may find this funny, but this is my amateur way)
monx said:
that file has system attributes. run this from command prompt to remove all attributes & locked attributes.
attrib -s -h -r -a filename.ext
your rgu file must hv unicode encoding, REGEDIT4 in line 1 & blank space on last line to avoid rgucomp error.
Hope this helps.
Click to expand...
Click to collapse
You mean
attrib +s +h +a filename.ext
then leave 1 empty line on the last line... do I have to add 1 space as well?
Just has to end with a blank line, rather than ending with a registry entry
Da_G said:
Just has to end with a blank line, rather than ending with a registry entry
Click to expand...
Click to collapse
Cool, thanks
Ok, I have successfully change the rgu file. It's one of these Lines, but I don't know which yet and I have no energy today to test 1 by 1 again... so if you can test it for me it would be great
Here are the lines that I've changed to make Call display work
Code:
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL] ; for HTCmaskW1
"HTCmaskW1"=dword:1871
"HTCmaskW1BitMask"=dword:FFFFFF
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL] ;for A5/2, A5/3
"En52"=dword:1 ; A5/2
"En53"=dword:1 ; A5/3
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL] ;for remove RX Diversity
"RMRXDiv"=dword:0 ; Enable
[HKEY_LOCAL_MACHINE\Software\OEM\RIL]
"DisH"=dword:2
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL]
"DisableAutoPickupAtSilentMode"=dword:1 ;disable by default
add ---> [HKEY_LOCAL_MACHINE\Software\Microsoft\RIL\APIInfo\69]
"Timeout"=dword:7918 ; 31 sec.
[HKEY_LOCAL_MACHINE\Software\Microsoft\RIL\APIInfo\82]
"Timeout"=dword:1D4C0 ; 120 sec.
[HKEY_LOCAL_MACHINE\Software\Microsoft\RIL\APIInfo\81]
"Timeout"=dword:1D4C0 ; 120 sec.
[HKEY_LOCAL_MACHINE\Comm\Cellular\RIL\RemoteCalltype]
"CalltypeDLL"=" PTTCalltypeCallback.dll" ; DLL containing the callback routine
[HKEY_LOCAL_MACHINE\Security\Policies\Policies]
"0000100c"=dword:800 ;Service Loading (SL) Message Policy
[HKEY_LOCAL_MACHINE\Software\OEM\RIL\OperatorContexts\20801] ;Orange FR
"GPRSContextNumber"=dword:2
"UMTSContextNumber"=dword:2
[HKEY_LOCAL_MACHINE\Software\OEM\RIL\OperatorContexts\20810] ;SFR (Voda FR)
"GPRSContextNumber"=dword:2
"UMTSContextNumber"=dword:2
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL]
"BattSuspendTimeoutBackup"=dword:3C
"BatteryTimeoutBackup"=dword:1E
"BattSuspendTimeoutInCall"=dword:30
"BatteryTimeoutInCall"=dword:30
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL]
"EnableIMSIAttachedIcon"=dword:1
Perhaps someone can pick this up for me since I'm not much of a registry guy.
Here is a weird thing that I found about this Tweak
When someone call, the ID will display and all... However, in Call history, it will only display the caller Name if it's a missed call. If you answer it, then it won't show the name ID in call history, but only the number... I'm testing it with FuzeBerry v6 theme. Can anyone confirm this?
and if you know how to fix this, it would be great
Ok, for this tutorial, I deserved a kiss
History:
you all know how I didn't sleep for 2 days just to find what needed to be done to make it work. Now after my 10hr sleep and a bunch of parties for new years, I finally found a way to do this without cooking anything. I need someone to test it for me thou. I've tested on NATF's and Elite's ROM and it works. If this work, a thank you would do.
The Basic:
The Main idea to make this work is to replace the rilphone.dll file and add some registry into it, like I was explained in the first post. Some people claimed that those files need to be cooked in, well, you don't however, you can't just replace rilphone.dll it just doesn't work that way. But I found a way
So How to do it?
1- Download rilphone+reg.zip file from this post
2- Extract the file and you'll find
+rilphone.dll
+rilphone2.dll
+rilphone.reg
3- Copy rilphone2.dll into your Device in \Windows\ folder
4- Copy rilphone.reg anywhere
5- Importe rilphone.reg to your registry (I used resco registry to do this)
6- Change this registry from your device
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL]
"Dll"="rilphone2.dll"
7- reboot
8- copy rilphone.dll into your device \Windows\ folder
9- Change the registry back to
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL]
"Dll"="rilphone.dll"
10- Soft Reset
11- Delete rilphone2.dll
12- Soft Reset
13- Give me a hug
***Please report which ROM have you tried this method with and if it works or not***
--------Edit---------
Ok, so it doesn't work for every ROM. It worked with Elite RC2, thou... I'll give it more tries tonight. Stay Tune
If you want to try this process, please make backup of rilphone.dll first
And please try to put step 5 at the end.
Instead of trying all this, try the cab on post #26... if it doesn't work, just uninstall it. Backup rilphone.dll first. Worst case, just do a hard reset.
---------------------
--------ROM tested with cab-------
- Elite RC2 -> Work
- Proven 1.08 -> did not work
- Romeo -> did not work
-------- I'm sick of flashing and hard reset, so I'll stop here. If you're already on other ROM. let me know.
Good to see you we're able to get this working.
I didn't modify any part of the RGU file in OEMDrivers, so I'm just gonna drop the new DLL and the RGU/DSM you provided here into my v4.0 kitchen.
NotATreoFan said:
Good to see you we're able to get this working.
I didn't modify any part of the RGU file in OEMDrivers, so I'm just gonna drop the new DLL and the RGU/DSM you provided here into my v4.0 kitchen.
Click to expand...
Click to collapse
Ya, it should work... however, can you check if the RGU/DSM file didn't affect QuickGPS? I didn't make any change there, but just check for sure.
Finally, I can sleep with ease now...
My next wish, somebody make a cab or 2 to make my previous post easier
Only problem with non-cook method will be, if target ROM is not cert patched, or doesn't have certificate loaded from rilphone.dll signature it will refuse to load rilphone.dll due to not being signed with a trusted cert..
hey pandaboy,
tried this on my fuze but didn't work, (using proven rom right now) my wireless radio stops working after. i even tried starting over by deleting your rilphone.dll file and softresetting to get my phone working and did the steps again. no go.
Same, my radio is not working now either. Is there anyway to get my radio back?
just delete the rilphone.dll file from your windows directory and perform a soft reset
y2whisper said:
just delete the rilphone.dll file from your windows directory and perform a soft reset
Click to expand...
Click to collapse
When i try to delete it it says cannot delete the file.