well.. here is the latest and greatest version of the rom koch.
its pretty close to the final version, there is one little (functional unimportant) bug thats why i do not release it as final.
i wont be around much from now on so if you need support go and bug pof or olipro
it is very easy, i have cooked alot of different roms now and i consider it stable and guess what i release it exactly on time!
have fun, if you need some last minute help drop by into our irc chat at irc.freenode.net / #xda-devs.. i will be around a few hours
i tried to keep track of my changes with a changelog, but as you can imagine i forgot alot of changes, but here it is anyways.. because im sure alot of you guys are interested in such stuff:
Code:
-after opening a rom, select button is disabled.. inorder to renable, start a new project
-console font changed to vista's segoe UI. don't have it? get it
-added the kochs own unicode text editor
-features, remind if forgot to save, right mouse, cut&paste etc.
-after editing a file and saving it will be moved out of the dump into the projects directory
-added menu bar (projects,console,?)
-restructured lower form layout
-browse for rom is grayed out after selecting a rom
-alot of internal changes necessary for project handling
-imagefs is beeing generated upon loading rom (part of project handling) if it already exisists for this rom/project
it will not be gerneated again
-inorder to load list of files in rom no dump of the rom is required anymore
using my new tool "listimgfs.exe" , the tool will be added to the official buildchain, source will be released
-new dumptool utility based on mamaichs viewimgfs, recmod is redundant now.
using this tool you can extract either one single file or create an complete dump
no matter if its XIP or a normal file
usage: extractfileimgfs <imgfilename.bin> <filename> (<outdir>)
<filename> can be '*' to dump everything
<outdir> is optional and defines the output directory for the dump
-even more internal restructuring because of the new project handling
-multiple fileselection in original romlist possible
-multiple file selection in add file to rom dialog
-another layout change
-new tool to decode/encode nbh files nbhtool.exe, get it while its hot
-imported nbh-classes into the kitchen, i.e. you can now decode/encode images without any external tool
<more things i forgot>
-changes and fixes to extractfileimgfs
-added searching to the editor
-added find again "f5" to the editor
-important project files are automatically extract upon project creation
-fixed initflashfilees editing
-fixed registry editing
-added find string to editor
-changed editor window type to toolwindow
*changing programm architecture, removing all external dependencies execpt rgucomp
-alot alot alot and alot of work on the image modification library :(
-prevented adding too many files
*alot more work done at the toolchain
**again million fixes and changes that i forgot to add here :(
-finally finished project handling, loading and saving a project is now possible
-fixed the select a rom button not beeing reenabled after starting a new project
-adding a file into the rom: if it already exists it will be marked for removal
-implemented a workaround for a bug in the imagefs library not a real fix but a workaround
-final cosmetic cleanups for v0.99
just try it, its a totally new tool
screenshots:
download: http://rapidshare.com/files/20594171/_romkoch_v099a.zip.html
update 12.03.07: fixed bug when compiling.. that causes a crash on xp machines
just incase you havent noticed, these "project", "console" and "?" labels right above the console are menus ; )
update 12.03.07 #2: pof detected a cosmetical issue - fixed. (extracting roms wont label them correctly)
Thanks dutty! Hope everything goes well tomorrow and hope to see you soon kicking ass here again!
A big THANK YOU from me as well. You're actually the first developer I met who constantly meets his release deadlines! Respect!
All the best for tomorrow!
Cheers
Daniel
tadzio said:
A big THANK YOU from me as well. You're actually the first developer I met who constantly meets his release deadlines! Respect!
All the best for tomorrow!
Cheers
Daniel
Click to expand...
Click to collapse
thanks alot.. incase you havent noticed.. i have just uploaded a revised version, please redownload it was a bug that happend when i renamed the file from cookgui.exe to koch.exe for the release and forgot to update the assembly names
Here is a picture of it running under XP pro.
J-Man5
incase you havent noticed. the file has been updated. thanks to pof and j-man
could someone put this on the FTP as I can not access "Personal Network Storage" sites from work.
done
check the hermes uploads directory for _romkoch_v099a.zip
Good luck from me too dutty! True XDA Guru's are always in short supply so we'll be needing you back right away plz!
Where do the "preconfig" files come from?
Sorry for being a bit off-topic, but I didn't want to start a new thread.
I used the ROM Koch to look into the new lvsw edition, which I also have flashed. When I hard-reset my TyTN and don't do an immediate soft reset, then all the xml and cab from \Windows\Config.txt are executed. Some of these files are indeed present in the \Windows folder of my TyTN.
However, they are not in the 06_OS.nb file, or at least the ROM Koch does not list and extract them. This seems logical, as the contents of these files is specific to HTC, and the 06_OS.nb is generic Microsoft.
The question is: where are these files, and how do they end up in the \Windows folder?
Thanks,
Daniel
thanks sleuth
tadzio said:
The question is: where are these files, and how do they end up in the \Windows folder?
Thanks,
Daniel
Click to expand...
Click to collapse
extended rom
well done on this tool dutty.... its has come so far...
good luck with your op mate...
dutty said:
thanks sleuth
extended rom
Click to expand...
Click to collapse
Still offtopic, but the lswv ROM does not have an extrom. The preconfig insrt (config.txt) in that ROM also does not execute the "autorun.exe" for an ExtRom to run. I looked at to see if HSDPA was set among others.
Well, I must correct myself - most of the files are in the Windows.nb now (either I was blind, or the first Rom Koch 0.99 version skipped them). Some are still missing, but I guess lvsw just removed them and forgot to delete them from the Config.txt, or they were never there in the first place.
The Extended ROM seems to have nothing to do with this.
Cheers
Daniel
Great Job dutty,
Best wishes, hope all goes well tomorrow and a speedy recovery. We will miss you here.
thanks everybody for the get well wishes.. i really appreciate that!
wpbear said:
Still offtopic, but the lswv ROM does not have an extrom. The preconfig insrt (config.txt) in that ROM also does not execute the "autorun.exe" for an ExtRom to run. I looked at to see if HSDPA was set among others.
Click to expand...
Click to collapse
oh.. yeah right.. the first lswv rom that was released had a extrom,ipl,spl and radio included.. but that one was pulled off the net quickly
dutty said:
thanks everybody for the get well wishes.. i really appreciate that!
oh.. yeah right.. the first lswv rom that was released had a extrom,ipl,spl and radio included.. but that one was pulled off the net quickly
Click to expand...
Click to collapse
What was in the ext rom? The Preconfig config.txt didnt reference the running of an extrom, so how was the extrom going to be automatically executed. Anyway, was there anything new int he HTC EXTROM of interest.
OMG! I can't wait to give this a try. Hope all is well dutty - good luck. And thanks for the great tool!
Hi dutty,
best of luck with the op.
Thanks for this tool, I think I can say I am comfortable to cook my own rom now.
I will give it a shot over the coming days.
Cheers
I have two questions, please don't judge me if they sound noobish:
1) Is this tool generic, as in can it be used to cook ROMs for other devices (like Trinity)?
2) Does this tool help when trying to make a dumped ROM flashable?
Related
Hi - first major post so bear with me!
After 'cookin' my own extended ROM a few times, I realised that harvesting the various CABs was only the first step - I then had to trawl this (fabulously informative) forum (and wiki) and identify each CAB to see if I actually wanted it in this particular ROM – sometimes I’d find a picture (really helps), and sometimes not, either way I would always forget what something was and have to re-find it.
So I wrote a utility to help me - and I'm sharing with everybody else 'cos that's just the kinda guy I am. XtendROM scans a folder (I’m old-school so I still call ‘em directories, but I’m trying to speak windoze here) and treats that folder as the ‘library’ – it is from there one can select which CABs you want to include. I’ve set things up for the Himalaya (I have an XDAII) so the default extended ROM size is 64Mb, although it only warns you if you go over that.
The principal is simple - deliberately so. Information on the CAB files is stored in TXT files and the preview images are stored as GIFs, BMPs or JPGs (always the same name as the CAB file, with an extra file-extension). I’m thinking that we could post TXTs/images and maybe even CABs in this thread, thereby making cooking a ROM as easy as downloading the CAB/TXT/image, saving it to the ‘library’ and choosing it for your ROM.
Drag & drop should work (to some extent at least) and the ROM files can be moved up/down in the config.txt file easily enough – after all I made this for my own use and getting the information from the web-pages is sometimes the trickiest part. I’ve recently added an option to copy the selected CAB files into a separate folder, this way I can easily copy the new files into the new ROM without having to search manually (computers ARE here to make life easier – allegedly).
Um, I think that’s about it – consider this a first-release so I’ve undoubtedly missed stuff, and I’m pretty sure I’ve forgotten to save some settings into the registry (I’ve had to get on with some real work, but this version works okay – mostly). Of course, if this utility kills your system, turns into potted-plants or does anything else I’m not expecting then you’re on your own – if you have doubts then don’t use it, I ain’t getting sued just for sharing my stuff.
I'll be adding some TXTs/images/CABs here myself at some point - I'm just too busy with other stuff at the moment (patience, I'm told, is a virtue).
Any problems, comments, questions or thoughts then please post here – knowledge is a thing best shared.
:edit: - I forgot to mention above, but when a file is copied the file-extension is automatically checked and the approriate command inserted into the CONFIG.TXT - for example, copying a .EXE file will default to 'EXEC', whereas a .TXT file would generate a CPY1/CPY2 command (to copy into \Windows).
Toodz,
- StarFux -
Excellent, let's me try and I will post my feedback later.
Thank a lot.
cool program.... downloading now...
thanks
No further comments?
Just checkin'-in... so, no feedback? Must be just that good then ...
-sf
Thank you krab.. Let's me try..
Some TXT files to get things started
Attached are some TXT descriptions from xda-developers - the zip-files are named according to the username of the person who wrote the text (all credit to them, not me) - I've just compiled the data into a format that XtendROM will make use of.
yann.zip - from http://forum.xda-developers.com/viewtopic.php?t=6470
sin.zip - from http://forum.xda-developers.com/viewtopic.php?t=16916
Just unzip into your chosen library folder.
S'all - have fun.
-sf
besides of having one error on my first run .. just forgot wat it is .. i think you've done a greate job .. now its much easier to create config.txt and to avoid .. further error if i created it in notepad .. btw tnx for the tool m8 ..
...very nice looking tool )))
THANX
buzz
What a great application
Thanks for sharing
Now maybe we can create all huddle together and create a central library for all known extended ROMs so we can cook our own ExtROM
Thanks for all the positive feedback! - I'm working on some tweaks to cope with creating compressed ROMs at the moment (thanks to some great feedback) - I'll post here when I've sussed it
Thanks again!
-sf
Giving up
Hi all - well excessive demands on my time from work & home have meant I've been unable to tinker with my util, so I'm giving-up trying to find time and have decided to sleep more instead.
If anybody else wants to play with it (it's written in Delphi 7 & uses a few libraries but could be played with), then PM me and I'll send you the source so that you may continue development (if desired).
Hope everybody continues to enjoy the util anyway - L8rz.
-sf
When LennySh had released a UC ROM I was looking for a UC Rom SDConfig.txt builder and found THIS. However, it would not even load on my Windows XP laptop... So i decompiled the program to get the source code, completely redone copy of original interface by hand (God, that was painful) and have seen numerous bugs in the code. I was going to report them to original developer, however seems like he doesn't work on this program anymore. So i decided to take this matter into my own hands and started developing this program further.
SDConfig Builder v0.7.85 PE (released July 16, 2008)
Features:
-- SDConfig.txt builder.
-- reg2xml converter (including special character/Unicode support)
-- xml2cab packer
-- xml preview/edit
-- custom Owner Information to XML
-- a few other things...
Known Bugs: I need your help finding them!!!
NONE known
Things to work on
1. Have to be 10000000% sure reg2xml and owner info generator work correctly. Need testers.
3. Built-in XML editor does not save by itself (but works fine with "Edit XML" button)
5. Have to make window dynamic (so it can go full size)
6. Make suggestions!!
Instructions to use
-- Unpack the archive to any folder
-- Make sure you have Microsoft .NET Framework v2.0 installed
-- Run "SDConfig Builder.exe"
-- Read documentation on XML and SDConfig.txt (Click link)
-- Have fun. Report bugs. Ask for new features.
Download (direct link. No wait time!) (250kb): SDConfig.Builder.v0.7.85.PE.rar
NOTE: Original project was started by doedoe and since then almost all of the code has been rewritten by me...
NOTE2: I'm 2nd year computer science student and my experience in .NET programming is limited to 30 hours so please DO NOT expect miracles from me But I will certainly do what I can...
Change Log:
v0.7.85 PE (July 16, 2008)
-- reg2xml: Fixed MANY bugs thanks to uzziah0 for pointing some of them out!
-- reg2xml: now has Unicode support (non-English characters, i.e. Russian, German, Spanish)
v0.7.8 PE
-- Completely redone "SDConfig" tab interface.
-- Added drag-and-drop feature for adding CABs & XMLs
-- Dag-and-move items in the list
-- Can now open existing SDConfig.txt files!
-- Many other new features...
NOTE: I have only made changes to SDConfig.txt part. Everything else is same as in previous version.
v0.7.21 PE
-- Fixed few SDConfig.txt save file bugs
-- Fixed Owner Info 2 XML bugs. Now works great =)
v0.7.1500.1 PE (Prikolchik Edition)
Bug fixes:
-- reg2xml now understands values that are taking move than 1 line.
-- reg2xml works correctly with hex values and converts them to base 64
-- xml2cab is now working correctly
-- fixed problem with saving SDConfig.txt (was placing '\n' character at the end of every line)
-- removed/added some notification windows
-- many minor fixes
New features:
-- XML-tester/editor. Please use "Edit XML" button on the top right.
-- Unicode reg file support
-- Owner Information generator. Please test it!
v0.6.3456.1PF (PF = prikolchik fix)
now works on WinXP (added workaround)
Added reg2xml feature
Fixed few notification windows
Fixed minor bugs
(everything below by Doedoe)
v0.6
Fixed Tab's at end of lines
v0.5
Fixed missing CABs & XML in output file issue
Fixed source CABs & XML selection issues
Fixed Move Up / Down experiance
Added Select All option in source files
reserved for more info
Sweet man. I def try this out in a few and report my findings. I'm glad to see that you picked this project up.
and by god.. u r good at it.. this is a wonderful face lift to the original proggy.. keep it up
wow! nice stuff, will defo try it...
also going to try it out, I love UC compatibility.
This looks great, but I'm looking for a little more instructions before I start.
Do I need the CAB files for this to detect, and if so where should they be (on my SD card or PC)?
Do I need to run this so it reads stuff from my Axim?
I'm just looking for a little more details in:
-- Read documentation on XML and SDConfig.txt (Click link)
-- Have fun.
because the other thread doesn't include those details either.
uzziah0 said:
This looks great, but I'm looking for a little more instructions before I start.
Do I need the CAB files for this to detect, and if so where should they be (on my SD card or PC)?
Do I need to run this so it reads stuff from my Axim?
I'm just looking for a little more details in:
-- Read documentation on XML and SDConfig.txt (Click link)
-- Have fun.
because the other thread doesn't include those details either.
Click to expand...
Click to collapse
Well, it is all much more simpler than you think =).
You just specify a folder on your computer with CAB files and program will read their filenames. That is what you will be operating with.
Program will not copy, or do anything with cab files, it only read the filenames.
It cannot read anything from your Axim (only the details, or whatever, that were originally made by Doedoe but were not tested by me due to lack of Vista)
The documentations in the link is about SDConfig.txt files. What they are and how they look. There is also information about XML files. That link does NOT have ANY instructions for using SDConfig Builder.
Also, just want to note that in a few days i will release a much better version of SDBuilder which should be much simpler to use.
I dont know if i should create any instructions for it, since it is all very straight forward... But we will see.
new version of SDConfig is posted. See first post for download link, description and screenshots.
nice work.. will try this on my next flash, probably tonight... lol..
progress
any progress on this great software??
madamada31 said:
any progress on this great software??
Click to expand...
Click to collapse
I dunno if i even should work on it. 500 downloads and not a single constructive comment. I dont even know what to change or improve... and if anyone actually finds in useful...
Why would i spend time on something nobody needs, when I can do something else that people actually need (non-PDA related)
this is a great app, its been saving me about 30 mins each time i flash, its good that i can just select the cab files to install just by checking the boxes.. keep up the good work...
not sure what to say on it needs to be improved
here is an idea... : if you look at Schap's Advanced config it is all about tweaking and such, but it only allows you to change it manually at runtime
However, if it could make those changes and export to XML/cab file so it could be stored in SDautorun....
prikolchik said:
I dunno if i even should work on it. 500 downloads and not a single constructive comment. I dont even know what to change or improve... and if anyone actually finds in useful...
Why would i spend time on something nobody needs, when I can do something else that people actually need (non-PDA related)
Click to expand...
Click to collapse
Wait, wait!!
I found this software today when I tried to find something that apparently is nowhere to find elsewhere:
What I need is a XML to REG converter.
Your first post is saying that exactly this is integrated since V0.6.3456.1PF:
prikolchik said:
v0.6.3456.1PF (PF = prikolchik fix)
now works on WinXP (added workaround)
Added xml2reg feature
Click to expand...
Click to collapse
Only I can't find this XML2REG feature in any version of the software.
Of course a REG2XML conversion is integrated, but not the other way around.
I would be glad if you could tell me how to use this because apart of a Pearl script which needs some libraries which are meanwhile not available for download any more I have found nothing that can handle this conversion.
Thank you very much in advance!
I played around with this software for about 5 minutes this morning, and I just wish I had found it a couple of weeks ago before setting up all my UC by hand... Lol... Oh well...
So far looks very good, I'm gonna test it some more and let you know if there's anything that can be improved.
One thing I'd like to see is a list of common reg entries that can be modified, and an xml created. Kind of like a schaps Advanced Config thing, but so that those settings that are chosen are done by the UC, instead of after...
what i woldn't mind seeing in this software is xml settings for all settings in control pannel... stuff like lights or sounds etc..... thanks in advance thats if u still wanna work on this program
thank you very much, prikolchik.
it is very useful. thanks again for your great efforts!
Silly question.. I've been reading over the various threads related to this.. does this process only work thru a UC compliant ROM.. or can I build a config file and run it after installing any ROM?
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
M-ROM v1.1
ROM Language: Dutch
Based on shipped NLD rom 1.90.404.1
But ROM updated to build 20755.1.4.0 (XIP/SYS ported)
and this has been done...
Updated:
- Net CF v3.5
- GoogleMaps (NLD) v2.2.0.19
Added:
- UC
- Alternate sliding sounds (transformers, star trek, etc)
- Advanced Config v3.3
- TF3D config v6.7
- TomTom Navigator v7.451.903
- Klaxon 2.0.19
- Lightsaber v1.0
- MS Voice command v1.6.19209
- WMRegOptimizer
Removed:
- removed introduction video
- removed customers feedback
- removed autoupdate
- removed Cyberon speeddial
- removed sample music / wallpapers
- removed MP3 Cutter
Tweaks:
- Disabled SMS-threading
- Disabled Security warnings when installing non-certified applications
- Many speed improving tweaks...
!! UPLOADED NEW VERSION (23/10/2008) !!
Working on M-Rom v1.2 (build 20924.1.5.0) Be patient....
Download DOWN! ! updated !
RAR-password: XDA-Forever
notes:
- I'm still deployed in Afrika without my TP so no chance for testing the rom myself!
- This ROM is UNprotected and maybe tweaked by everybody to fit their own needs! background discussion found here
Looks like I've wasted my entire Saturday morning by doing the exact same thing!
Well done though merten3000 - much appreciated!
Great
Good work.... many thanks for the contribution mate...
Anyone feel like adding this to the wiki?
mrvanx said:
Anyone feel like adding this to the wiki?
Click to expand...
Click to collapse
Wait for some reactions first...like I noted I could not test the ROM myself...unfortunatly
Maybe it is full of errors or does not even boot...still a cook no chef...
Excellent. I'm gonna try it tomorrow just to see if I can teach it to speak Czech.. big tu.
And? How the ROM? Anybody tested him?
mattcrow said:
And? How the ROM? Anybody tested him?
Click to expand...
Click to collapse
My thoughts exactly...
i will givde it a try 2morrow. i'll post back here.
I just flashed your ROM but I cant get over the first screen - The one that says the versions in the bottom. Have been waiting to get the phone booted for over 5 mins already.
Back to my Pdaviet ROM I think.
Edit: Yep, flashing previous ROM (Pdaviet) from card.
crocodile010 said:
I just flashed your ROM but I cant get over the first screen - The one that says the versions in the bottom. Have been waiting to get the phone booted for over 5 mins already.
Back to my Pdaviet ROM I think.
Edit: Yep, flashing previous ROM (Pdaviet) from card.
Click to expand...
Click to collapse
So the flashing went well, but after that the reboot did not work? Damn!
It's sh*tty that I can't flash myself to test.
Maybe another cook can take a look as it is unprotected...
tbh it sounds like a symptom of not porting the XIP across correctly, i'll take a look and see if theres some overlap errors.
EDIT:: I see no overlaps in the maps list however i cant be sure the XIP is a functional one. Im wondering did you port the XIP across using the normal technique or was it just a straight copy and paste from the doner device?
mrvanx said:
tbh it sounds like a symptom of not porting the XIP across correctly, i'll take a look and see if theres some overlap errors.
EDIT:: I see no overlaps in the maps list however i cant be sure the XIP is a functional one. Im wondering did you port the XIP across using the normal technique or was it just a straight copy and paste from the doner device?
Click to expand...
Click to collapse
I extracted xip.bin from a functional Raphael 20755 build and merged it in the payload using write2 option in xiptools. Because it was a working Raph rom I thought I did not need to change the device-specific OEMkernel? Maybe I thought wrong?
p.s. When I was looking for the problem myself yesterday I noticed that in boot.rgu (in ROM folder) the the MUI values keep changing back to 409 instead of 413. I changed them many times, but when I build the rom and dump it again, it is changed back to 409??? I already went through the hives and boot.ms.rgu but can not find those entries there...
The only thing you need to do is to put the .nb (which you want to use the XIP from) into the ROM folder, the build process will take the nb and replace only the OEM and SYS components in it, so aslong as you port the SYS across correctly then the XIP will be in the nb correctly.
Just to make sure though did you write the xip into the os.nb.payload?? (you cant write it into os.nb, it must be the payload section of it, also make sure the address is 03200000 instead of 03100000).
mrvanx said:
The only thing you need to do is to put the .nb (which you want to use the XIP from) into the ROM folder, the build process will take the nb and replace only the OEM and SYS components in it, so aslong as you port the SYS across correctly then the XIP will be in the nb correctly.
Just to make sure though did you write the xip into the os.nb.payload?? (you cant write it into os.nb, it must be the payload section of it, also make sure the address is 03200000 instead of 03100000).
Click to expand...
Click to collapse
Thnx again, I will look into it and repost if I succeed..
I did use the payload, but will check the adress to be sure!
! UPDATED FIRST POST !
Downloading and ready to flash
(if RapidS**t will speed up)
edit: The way Rapidshare has been behaving, could you give a md5 / crc check?
I like to be sure to have the right file, without faults.
(I'll test it anyway, got ROMeOs1.13WWE ready, after being happy with 1.12WWE)
edit 1: Flashed perfect, but again no boot, hangs again at the first screen
There is something wrong at boot time, flashing to ROMeOS 1.13 now.
(Just ask me, will try again, I can give you some space to upload to )
edit 2: up and running again
karloe said:
Downloading and ready to flash
(if RapidS**t will speed up)
edit: The way Rapidshare has been behaving, could you give a md5 / crc check?
I like to be sure to have the right file, without faults.
(I'll test it anyway, got ROMeOs1.13WWE ready, after being happy with 1.12WWE)
edit 1: Flashed perfect, but again no boot, hangs again at the first screen
There is something wrong at boot time, flashing to ROMeOS 1.13 now.
(Just ask me, will try again, I can give you some space to upload to )
edit 2: up and running again
Click to expand...
Click to collapse
Thnx for testing man...but WTF is wrong woth this rom??
Need some expert help I think:
- 1) I used a 20755 XIP whitch I manually changed to raphael (Kept original raphael Oemkernel). Used xipport to dump the XIP.bin files, made packages etc. But when recompiling the xip_out.bin each time I got errors that .txt files where missing for some of the package maps. But I did not touch those files. Anyway no luck with recompiling a working xip.bin
- 2) Almost same as above but did not make packages. In dump folder replaced all the right files (kernel + kerneltk) and again kept original OEMkernel files. Then I was able to recompile a XIP.bin but xipport created a file witch was 4/5 the size compared with the original one...that's no good I think also. So no luck this way
- 3) Extracted a xip.bin from a WORKING raphael 20755 rom using the raph kitchen. Merged it into the payload file using xiptools (but could not input adress there 003200000....?) That was the first version I uploaded.
- 4) Yesterday I used the extracted xip.bin again. But this time I merged it directly into the os.nb file to the right adress (003200000 instead of 003100000) using XIPPORT. That is the version I uploaded yesterday
Can somebody tell me what I'm doing wrong?? I'm getting quite desperate right now...
Any help is appreciated!
karloe said:
Downloading and ready to flash
(if RapidS**t will speed up)
edit: The way Rapidshare has been behaving, could you give a md5 / crc check?
I like to be sure to have the right file, without faults.
(I'll test it anyway, got ROMeOs1.13WWE ready, after being happy with 1.12WWE)
edit 1: Flashed perfect, but again no boot, hangs again at the first screen
There is something wrong at boot time, flashing to ROMeOS 1.13 now.
(Just ask me, will try again, I can give you some space to upload to )
edit 2: up and running again
Click to expand...
Click to collapse
Again after some tips (thnx MrVanx) I spent a whole night working at the ROM.
I revised the XIP and SYS totally and I think it maybe will work this time (it would be about time!)
Will upload tonight as I will not be around during the day
Karloe: I wil use rapidshare again, but pm about your privat upload space, thnx
What do you mean with unprotected rom btw
Like rome os with tweaks,other software and stuff,or something special?
Thx in advanced,greetings martijn from the netherlands also
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.