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.
finally i got the most turn off things i faced in 2005 to back me up to 2003 but after i installed 2005 for the 4th time & desided to stick with it untill i either solve the problem or microsoft will post solution
1. Etisalat Settings for mnet & MMS
(everytime you install them they somehow crash the original DB of messaging where you will not be able to open your mesages anymore untill you do a format
2. and most importantly Arabic reading writing
after long time spent to fix those problems i finally got them working, see screen shoots
yeah ok , great but how u fixed the issues ?
lol am sorry it was a bit hard, & even worse to explain, i writing down something that might help people around doing it once i find an easy way to make it accesseble to people
Rabia said:
lol am sorry it was a bit hard, & even worse to explain, i writing down something that might help people around doing it once i find an easy way to make it accesseble to people
Click to expand...
Click to collapse
Post a cab or tell us what you modified in the registry!!!
Waiting, thanks! :?
Oh something else I noticed the radio rom is 1.08.00, can you dump it?
PC) folder, take a copy of your registry after pasting the file & before softreseting the the device, then reset your device, if it will ask you then if you want to run few DLL files acept all of them, then take another copy of your registry & store it in a differant file, now go to your programs & you'll find arabizer file there in which one of them is english name, another one is arabic as '7ayarat & the 3rd one is arabic letters but mirrored in reverse, this will be always your indication if arabic is now working fine, click on this file, it will load couple of other DLLs but will give you some error message about an AOP????? file, don't mind it, now got to your control panel, (Setting) of your mobile & go to the settings Tab, again it will ask you to load some file.cpl say yes, soft reset your device with a software for soft reset not through the pen, then it will load, if you get an error about some file couldn't be loaded just reset few times & it should work, if you lost you signal in gsm, load the first registry file & softreset your mobile again, it will ask you to load some dll file again accept them then go to the settings to load the cpl file, then reset , if this doesn't work load the second resitry file & do the same proccess untill the file with the names reversed is corrected, now enjoy arabic on your system.
اود التنبية على انني لست مسؤلا عن اي مشكلة تطرأ على جهازك و العملية متعبة جدا
PS. if some get this way working for him i please him to put it in a simplified way because unfortunatly i have too little time to spare on rewriting it in an organized way, but once it worked i had to post it here because this is the best site in the world for PPC's & they deserve the best
Thanks mate I'll give a try later on
now that's interesting , thank u
anyone tried it guys am intrested to know
i think the secret is in the registry integrity & the file loading proccess, if you load the arabic files first after reseting the device they will affect the memory or the gsm loading, specifically the file CPROG.EXE which don't get loaded correctly, actually this is how i found i can fix arabic if i only get it loading after cprog & not before, thats why you put the files manually without the setup file so after you reset the device & when it asks you to load the dll files it will insert it in the registry after loading the cprog not before
guys i heared someone tried it withought backing up the registry & it worked perfectly fine, remaining only is the camera & record button & this should be it for me
i think the camera is the last problem , buttons are working fine 8)
Rabia said:
anyone tried it guys am intrested to know
i think the secret is in the registry integrity & the file loading proccess, if you load the arabic files first after reseting the device they will affect the memory or the gsm loading, specifically the file CPROG.EXE which don't get loaded correctly, actually this is how i found i can fix arabic if i only get it loading after cprog & not before, thats why you put the files manually without the setup file so after you reset the device & when it asks you to load the dll files it will insert it in the registry after loading the cprog not before
Click to expand...
Click to collapse
sadly it didnt work for me,the device kept hangings on the splash screen,I tried it with wireless on and off, i did hard reset 5 times (2 with clear registery option) but nothing worked,I also upgraded to Radio 1.17 but still didnt work,I couldnt find out what's going wrong (I get prompt to overwrite 3 files while copying them into windows folder) WM2005 1.50h, Radio 1.14 then 1.17
well am not sure but regarding the hard reset only do the clear registry hive option without the format,
hi guys!
we are working for the localize Himlaya WM5.0 to Chinese and Japnese.
On the previouse OS, we need Font and registry, and also need wince.nls which support to encoding to our languages.
without replacement wince.nls, the inbox and IE cant encode to ours.
Usual, we got the wince.nls which has our lamguge support from the device of Japanese or chinese, or take from SDK emulator, or make it ourseleves with MS Platform Builder.
Till the version of WM2003se, easy to replce it.
But new OS of WM5.0, replacement of wince.nls can not be effected, even it was replaced firmly. the OS seems to be ignor that!
@On the Himalaya WM5.0, Some version such like 1.6b, 1.6h, 1.6i can get encooding with new wince.nls, but other version of WM5.0, it was not be able...cant find the reason yet.
@On the Blue Angel WM5.0, also it was ignored by OS
@On the Jasjar just we got, also it was ignored..........
We need find some solution of this system which ignore the replacement of wince.nls.
i already work for that more than 5days ........
I think to localize to Alabian, you guys will have same problems.
Example some of you can replace wince.nls, some of you can not get it.
so if you got some information, please exchange it about that, of course we also let you know if we got it!
Thanks guys!
following is our thread about localize to Chinese / Japanese..
You may know what happened on new OS.
http://forum.xda-developers.com/viewtopic.php?t=24781&highlight=
here it is guys
did it
check it out
http://forum.xda-developers.com/viewtopic.php?p=160111#160111
1.6c
yes. I am using WM5 1.60C WWE, I can not replace the wince.nls in rom with new one.
this is again a simplified version of installing arabic in your WM2005, just install both attached cabs in there sequence & everthing should be working fine
PS am not resposible if it crashes your device but so far it haven't crashed min
to Replacement wince.nls
PLS install this cab,
and place your wince.nls onto \Temp folder
then soft reset. you can replace wince.nls
<exactry saying, not relace.enable to read wince.nls from \Temp frolder>
Rabia, what's so different about your arabizer version?
ramram said:
Rabia, what's so different about your arabizer version?
Click to expand...
Click to collapse
its the same as my earlier version but before people comlaint about arabic keyboard not getting installed & the need of using a 3rd party arabic keyboard for it to work, also some people had trouble over writing few files & so HOPFULLY this makes the installation far more easier untill Mr Imaginet company decides to develop a fully intergrated 2005 arabizer
Imaginet already created the arabizer for 5.0, but they didn't release it yet as you can see in the JasJar arabized version, we have a new built of arabizer
Simple steps on howto
1. download the kitchen Download
2. download Prophet Touch X rom Get it here
3. extract Kitchen and Prophet Touch X to separate folder
4. Place the OS.nb from Prophet Touch X in the rom folder of the Kitchen
5. run Buildos.exe and choose what to include (the marked apps are the once that are in Prophet Touch X) press the green play button and wait for it to finish
6. run CreateROM.bat (if there is any error the you have included to much in the Buldos prosess)
7. if there were no error the new OS.nb is in the temp folder move it to the Prophet Touch X folder and overwrite the os.nb in it
8. flash any step 1 WM5
9. now Flash your new rom within Prophet Touch X folder
if everything is done right you should have your new coocked rom on your Prophet
I have put all the things that should not be removed into the SYS folder so do only make changes to the OEM folder till you know more about cooking .
replace the HTC Audio Manager with this one
View attachment OEMAudioManager.zip
New HTC Album with folder option
View attachment HTCAlbumFolderOption.zip
Extras and links
I'll upload some addons for the kitchen later on as I've made more OEM packs
You can also search for oempacks to include but be aware that some OEM packs are device depented
Some cool tools that I use but have not included in kitchen You'll need to understand what they do before using them
HyperCore Kitchen cool for dumping roms and building ( I use it for dumping)
this is great.. awesome.
Great job Gullum. Now guys, we all should start frying Hokienmee or Char Kueh Teow (both chinese cuisine)
geney said:
Great job Gullum. Now guys, we all should start frying Hokienmee or Char Kueh Teow (both chinese cuisine)
Click to expand...
Click to collapse
I like both of them..LOL..
Really love this kitchen...
Thanks man, you are great!!!
It'll be even better if have a list of what those things really for. I do not know which box to check and which one is not
Maybe I'm too new for 'cooking'
geney said:
It'll be even better if have a list of what those things really for. I do not know which box to check and which one is not
Maybe I'm too new for 'cooking'
Click to expand...
Click to collapse
hold the mouse over one of the options and there should show and explaination for most of the items
good news
i'll try it
for every change in X and flashing it, is it always necessary to do step 1 again (wm5 flashing) ?
When I do hard reset and at the "tap screen to go on" point, I could start flashing X too ?
What I mean, is the complete rom exchanged when I flash X, or do some parts from wm5 or old X (IX, VIII ....) remain ?
I've try to cook today.. BUt seems something is going wrong...
Better I flashed it back to the original touch X ROM...
I also had some bad luck with cooking.
I did everything gullum said, flashed 'new' TouchX, did hard reset and then when its time to see welcome screen and 'press any key.....' there is blank white screen! Nothing happens no matter which button i press! Any ideas?
mcupurdija said:
I also had some bad luck with cooking.
I did everything gullum said, flashed 'new' TouchX, did hard reset and then when its time to see welcome screen and 'press any key.....' there is blank white screen! Nothing happens no matter which button i press! Any ideas?
Click to expand...
Click to collapse
I did the same think.
At my case, i have enter today screen.. But I think, its programs don't install clearly.. (hard reset don't help either.)
The first screen is the same one as you.. The white one.. Maybe you should to try ask Gullum again..
I just flash back to Touch IX with another Ext ROM. QuickMenu in that ext.ROM
thanks gullum
I would like to translate this rom to Portuguese can you give some advices? our some tutorial to do that, please? can i do that with this soft?
best regards
thanks (for this perfect kitchen) gullum ,some 3 questions i have :
1.>how to get oem or make one ,and
2.>how to get .dsm , .rgu files of my favorite software . and
3.>how do i make registry changes prior to build os are they automatic
Note :ext_rom files attributes should be read only since its like that in original rom so i made them read only(i think its healthy for system files any virus won't be able to modify it unless the file needs to be appendable updateable it should be read only),plus i deleted alot of thumbs.db files lying in many folders (about >2mb) just to clean oem folder files off thumbs.db i know winxp might be making them all the way .
i corrected audio manger with this kitchen (its gr8),i can't seem to solve camera album (have solved solution given below )problem ,it seems to have come back you know i can't use gestures , what to do ,any reg setting solution.
Edit : **corrected** the setting in reg hklm\software\htc\htcalbum\cacheserial to 2130706432
and hklm\software\htc\htcalbum\default_viewer to 0
if it still don't get solved set first 11 enteries (h_enable to v_pos) value to 0 in
hklm\software\htc\htcalbum\touchscroll\htcalbumclass
i'll try to provide a cab but this forum has alot of intelligent members
BuildImgfs
whatever I include in the buildos I am facing the same error when I try to create rom; something about BuildImgfs
any help guys!!
ma3ayta said:
whatever I include in the buildos I am facing the same error when I try to create rom; something about BuildImgfs
any help guys!!
Click to expand...
Click to collapse
2 reasons 1.> i hope you are pressing play(top left in build OS)button after whatever you choose,with what ever you want in it.
2.>your file size has to be limited its almost full with this kitchen so you have to remove some item like voice dialing (which i seldom use) or some other item removed before you add some item since size dependency is very important here ,and later run create rom .remember you cannot select everything because of space limitation .
Hello Gullum
I'm trying to do very basic thing adding Windows Live package into the OS.nb but it fails during CreatROM.bat. At BuildImgfs.exe the application BuildImgfs.exe crashes and show the error message and whether to send a report to MS or not (I don't send...).
I just directly add Windows Live to your OS.nb. Is it already fully loaded? Should I remove something before?
question with task manager
something is wrong with task manager.
in control panel ,its setting doesn't work!
Same problem.
Whatever i select in buildOS, BuildImgfs crashes.
Last records is CreateROM.bat window is:
Processing "Painting.gif" as file
Processing "S5K3BAFX.dll" as file
Processing "3aca900a-0834-11dc-8314-0800200c9a66.dsm" as file
Processing "c7dbe475-1d17-4fbf-a63e-af6dc042569a.rgu" as file
Processing "c7dbe475-1d17-4fbf-a63e-af6dc042569a.dsm" as file
Processing "-жE+-A+?.txt" as file
I think reason in strange file name -жE+-A+?.txt.
BINGO!!!
I Found this file in Prophet Touch kitchen.
\\OEM\Quickmenu\-жE+-A+?.txt
Just delete it before kitching.
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.
Hi
I have been cooking ROMs for a week or so now and all has been great. I can't recall making any major changes, but I now get the following when the phone does it's initial boot (and every boot after that)...
"The file 'poutlook' cannot be opened. Either it is not signed with a trusted certificate? or one of its components cannot be found..." And I can't do anything. i have searched but i have nothing found related to this problem
I am using (and have been using) IOLITE 20765 ROM and SYS and OEM 5.50.
I have made no major changes - I was testing other ROM's and SYS's, but I have reverted back to 20765 and I get this error - I never got this error on the other versions of ROM's and SYS's.
I have also redownloaded the files and created a new Kitchen folder to cook in...
Please can someone help???
DT
An update.
Redownloaded SYS, ROM, OEM and Kitchen 1.2b and started from scratch. It now works, so I am not sure what the heck I did to the other folders ...but I am sure glad it is functioning again
Can anyone tell me how to associate extensions with a program? any images I have defaults to opening them in the Camera app (not sure why) - I want them like before - except I am not sure what app the standard WM6.1 opens images in - can some one advise please?
Thanks
DT
d_train said:
...but I am sure glad it is functioning again
Click to expand...
Click to collapse
That's why we have HardSPL. Some cooked ROMs will not even boot. In those cases, take battery out, replace battery, turn phone on with camera button held down. This will drop phone into bootloader mode and allow a new ROM to be flashed.
Can anyone tell me how to associate extensions with a program? any images I have defaults to opening them in the Camera app (not sure why) - I want them like before - except I am not sure what app the standard WM6.1 opens images in - can some one advise please?
Click to expand...
Click to collapse
These associations are done in registry. For packages, you need to hunt through the kitchen for the registry and make the appropriate changes.
When I needed to change association for videos to TCPMP, the way I took was:
1) Snapshot of registry
2) Ran TCPMP. Made the association changes in its options.
3) Resnapshot registry.
4) Compare the changes.
5) Scan through the entire kitchen and find and substitute the registry keys in the RGU files and also .dat files
6) An alternative is to create a registry change, to be applied after the main ROM is built (or run at first bootup) like all the registry packages.
Total Commander is great for this. It allow search of strings of text within files in a folder and display all files with the search text. It also allows comparison of 2 files, and highlights the differences. Good luck. This is very time consuming.