Related
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?
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.
First things first! As the topic states, this is a *TEST ROM*
DO NOT expect this ROM to be usable for every day use
DO NOT expect this ROM to be well tweaked for performance
DO NOT expect this ROM to ... you get the idea, i hope!
This is the first Test ROM for the Image Update service - this ROM has a 1024KB free space buffer for NK partition, 20MB free space for OS partition. This should be enough to facilitate several ImageUpdates for testing. (It's not intended to have enough space for you to add all your chosen apps for every day use - this is just for TESTING!)
It's based on WM 6.5 21812. This ROM is unique in that both the NK and OS partitions are completely uncompressed, rather than using either XPR or LZX - so i'm testing that too. Please report on overall system performance of the BUILT IN applications (not cabs or packages you install) - i'm wondering if Uncompressed is viable at all vs. XPR and LZX. So far i'm thinking no (60MB LZX -> 80MB XPR -> 150MB Uncompressed) - but testing is warranted!
The Image Update packages for this ROM are now in post 2!
Here's the download link!
Again, this is BAREBONES, the ONLY thing it has is drivers and comm manager, this is done on purpose, so that we can have as few variables as possible while testing deployment
http://rapidshare.com/files/244900505/ImageUpdate-ready-ROM-Raphael.rar
Some notes:
The ROM has an OS pagepool size of 26MB
The ROM has a ULDR pagepool size of 4MB (up from 1mb)
All compression is disabled entirely (not XPR or LZX, but Uncompressed - both on NK and OS partition, also compression is disabled on individual modules and files)
Dr. Watson (Error reporting) buffer reduced from 300K to 0K
Update Packages
QuickGPS
EzInput+eT9
Camera - This will install the Camera, Dshow, Mhub, and SensorSDK packages (Camera is dependant on the others)
Here's the test case scenario - create a directory named "Release" in your filesystem, at the root \ folder (so \Release)
Copy the cab.pks to your device, or sd card, and run it as you would a cab
Note any errors or anything that might occur before the process succeeds or fails
If the process fails - please attach the logs found in \ and \Release to a post, so we can analyze it further
If it succeeds, time to hard reset your device!
Check and see if the package remains after hard resetting.
If it does - We have a winner
A live-updating rom with no need to reflash the device after each upgrade? I love it!
Keep up the good work!
Interesting concept.
this is awesome! cant wait to cook one for kaiser(hint, hint) thanks for all your work, this is going to change EVERYTHING.
Image Update System
I have been following the WM Image Update System thread and the idea sounds very doable. How can we help?... David.
I can Hard reset my phone every day, so if you in need of any volunteers Im here .
I have been following your kitchens for a while, and it's time to return the favor.
Thanks so much for your hard work Da_G!!
-------
HTC Fuze - WM6.5 21812
Da_G...Sir, you are a saint and a scholar...when this is finished it will be the coolest thing since velcro...
I would love to help just let me know how...would be happy to test..report...etc.
Dreaming of the day...no more hard reset
Da_G,
Thanks for your hard work.
I'll been dreaming of the day when I don't have to reflash my ROM or hard reset just to update the software.
I'll beta test and give you report.
D/Ling now, will report after work this evening. :excited:
i am really enjoying the speed. its unreal. every thing else seems normal. i am still loading up my apps right now. i'll post up some more when i get home.
the speed and respon se is secon d to none . i am very much plea des with the performance .
i know you said its barebo nes....so. i will view the lack of came ra e xe and .net. fram ework as by design . let me know if there is anyt hing spe cific you want me to test .
rzanology said:
the speed and respon se is secon d to none . i am very much plea des with the performance .
i know you said its barebo nes....so. i will view the lack of came ra e xe and .net. fram ework as by design . let me know if there is anyt hing spe cific you want me to test .
Click to expand...
Click to collapse
I'm going to need you to test your awesome space bar, it seems to be more than working well... =P
LOL, didn't overwrite CompIME.dll in this release (again for compatibility reasons) so that's why the jacked up spacebar..
But hey, it's a test
Hoping to have packages for you soon
Everything is working smoothly, no issues yet. I read your other post on the image update and want to know how far into user customizablity we can go without messing up the update process, ie. regedits, packages, etc.. Or if its a secure core that we can't really mess up.
Oh, yeah, its supper snappy and extremely responsive. And running at 26% Memory isn't bad either.
Is it safe to assume any updates needed to be deployed, such as over writing the CompIME.dll will be done thru the this new Updating system, correct?
Thanks for your hard work Da_G!!!
So, am I correct that any chefs who want to incorporate the working updating system into their roms will have to cook unprotected? This could get really interesting, LoL.
Thanks for the awesome work!
@Farmer Ted:
Yes, to support Image Update, ROM's will need to be fully "unprotected" - protection is really just damage to the ROM structure that still allows the phone to work
@NFRCER:
Yep, that will be one of the first test packages probably
@danthman2000:
The only thing you need to be concerned about in doing mods is that any files you replace or registry settings you change that might be in a future update, the update will not apply them, unless its specifically set to override your settings by using an mxipupdate_*.provxml - but the creator of the package should be aware of this before hand - so if it needs to override any of your settings it should be set to.
By the way, I plan to have the first test .cab.pkg up by tomorrow, so if you're sitting there with the test rom flashed, might wanna go back to a working one for now
Da_G said:
@Farmer Ted:
Yes, to support Image Update, ROM's will need to be fully "unprotected" - protection is really just damage to the ROM structure that still allows the phone to work
@NFRCER:
Yep, that will be one of the first test packages probably
@danthman2000:
The only thing you need to be concerned about in doing mods is that any files you replace or registry settings you change that might be in a future update, the update will not apply them, unless its specifically set to override your settings by using an mxipupdate_*.provxml - but the creator of the package should be aware of this before hand - so if it needs to override any of your settings it should be set to.
By the way, I plan to have the first test .cab.pkg up by tomorrow, so if you're sitting there with the test rom flashed, might wanna go back to a working one for now
Click to expand...
Click to collapse
A working one? This one is working beatifully lol .
Im curious, I checked the system tab, and I didnt see the Windows Update Icon...
How will we check for the update then? Just wondering, thats all.
My apologies if im asking too many questions
Great news Da_G. I'll test it once you post the update tomorrow. How do the updates get delivered?
Is the .cab.pkg a small file which contains the server information so the phone can go out and retreive it? Or is the .cab.pkg the whole kitten caboodle?
Hey all -
If you are looking for build 23025A, please see Post #3.
Here's 23017B. On my initial boot, I have over 29.5 meg free after running Oxios.
WHAT'S NEW IN THIS BUILD:
A new splash screen (thanks to eigerzoom)
Replaced psShutXP with PowerOptions - this has a functioning shutdown feature, and a few other neat tricks
Replaced Oxios Hibernate with the complete Oxios Suite - this also include Oxios Close-Apps, which will free up even more memory (but will close all of your open apps)
DOWNLOAD LINK:
Click here for 23017B (with white taskbar icons)
Click here for 23017B (with a colored taskbar theme)
Here's a list of some of the things I have included:
Memory and battery meter
Updated video drivers
Stock start menu
HTC Task Manager
Advanced Configuration 3.3
Total Commander
nueLED
Oxios Suite (Hibernate and Close-Apps)
PowerOptions
PocketRAR (automatically set as default for .zip and .rar)
AutoRun (UC)
Bluetooth Explorer
Fixed Comm Manager (both in button assignments, and Systems menu)
New splash screens
Built carrier free (see note below)
And a few personal tweaks - skinny scroll bars, ClearType enabled, larger fonts, the old IE set as default, ReplyAll fix and a few other things.
PLEASE NOTE:
This ROM was built carrier free. You MUST install a carrier cab for this to work. Find your carrier cab from here:
Carrier cabs
TO ENABLE MMS:
Here are a few cabs I have found on here and ppcgeeks that should help you enable MMS (multimedia messaging - pictures/video messaging). If any of these do not work, or if you have a better cab or a cab for another carrier, please post your information and I will update the catalog. I cannot vouch whether or not these work and am relying on you to verify. Please make sure you only install the cab designated for your carrier.
MMS cabs
I have also put together a few of my favorite programs that I install afterward to share. Please look through and enjoy!
Ivan's Collection of Handy Programs
Many many thanks to bbsandkm, mattsm, TPlane37, Joojoobee666, the PPCK team, the authors of all of the cabs linked from this post (I take no claim or responsibility for them) and everyone else who helped me along the way.
Click here to chat with us on our IRC Channel if you need immediate assistance.
Any changes either major/minor now that we've moved to the 23xxx build number?
Any fun screenshots or just the same old stuff?
Until I feel these latest builds have become fleshed out enough to become stable, I will keep them here in the third post. Please keep in mind that anything from this post is not entirely functional and meant as a preview only. I recommend having a stable ROM handy to revert back to after you are done testing.
The current build is 23025A. I have 4 different versions available for you. For the most part, the builds include the exact same programs and tweaks as the builds in Post #1. Here are the links and differences:
23025A - white taskbar icons & no HTC Task Manager
23025A - colorful taskbar icons & no HTC Task Manager
23025A - white taskbar icons & yes HTC Task Manager
23025A - colorful taskbar icons & yes HTC Task Manager
Please keep in mind that having the HTC Task Manager in these new builds is a double-edged sword. It works partially, but causes some distortion in the top taskbar; that is why you have the option to use it or not.
btonetbone said:
Hey all - Here's my 23001 build!
Click to expand...
Click to collapse
Good for you Mr boner.
While the chef's keep changing, thankfully they pass along their recipes. So the final meal keeps getting better and better.
Welcome to the cooking club!
Here's my 23003 build! It's includes very similar programs and tweaks from my previous, but I have removed the Adobe PDF Reader. Download, flash and enjoy!
http://www.4shared.com/file/116232830/e9bb90dc/23003-btonetbone.html
PS - I am accepting submissions for additional tweaks and/or splash screens you would like to see in future builds!
i want outlook to have a "Reply" instead of "reply to all" on the bottom left, i had a 6.5 build a few months ago, and it was the "reply to all" which sucks..
thanks
yznhmr said:
i want outlook to have a "Reply" instead of "reply to all" on the bottom left, i had a 6.5 build a few months ago, and it was the "reply to all" which sucks..
thanks
Click to expand...
Click to collapse
I agree it sucks. I'll look into a fix and see what I can do (but I was under the impression it is actually built in to poutlook.exe, so I'm not sure if there is anything that I actually can do).
OK, I fixed the Reply All issue. If you want to replace the left softkey in Outlook from Reply All to simply Reply, it's a simple reg edit that will go into my next ROMs. In the meantime, here's the edit and a cab which will do it for you:
Code:
[HKEY_LOCAL_MACHINE\\Services\OutlookEnhancement]
"Dll"=""
Enjoy!
Good find and good share man! I will be throwing that in as well. Who wants to reply to all lmao. What a dumb feature. I could see if you could select a few messages then click reply all but..
RyanMogul6800 said:
Good find and good share man! I will be throwing that in as well. Who wants to reply to all lmao. What a dumb feature. I could see if you could select a few messages then click reply all but..
Click to expand...
Click to collapse
No problem. I just put this up on my ppcgeeks thread and was going to send you a link. Glad you saw!
Here it is!
23004 - http://www.4shared.com/file/117005703/610b3d4e/23004A-btonetbone.html
I have kept the same programs from 23003, added the ReplyAll fix and added AutoRun (UC).
Enjoy and please post feedback!
Please forgive me if this is a dumb question, I have been searching the forum trying to find out what to do with this .nbh file. But I cant figure it out... I found some things on google but Im not sure and I dont want to brick my phone. please advise.
ouellettesr said:
Please forgive me if this is a dumb question, I have been searching the forum trying to find out what to do with this .nbh file. But I cant figure it out... I found some things on google but Im not sure and I dont want to brick my phone. please advise.
Click to expand...
Click to collapse
No problem. If you have never flashed before, please be sure to read the wiki:
http://wiki.xda-developers.com/index.php?pagename=TitanRecentHome
It has some fantastic information and will guide you through all the necessary steps to unlock your phone, upgrade the radio (if needed) and load a new ROM.
I have the .nbh named TITAIMG.nbh because that is what's needed for an SD card flash. If you'd prefer to use the ROM Update Utility (available in the link I pasted above), you will need to rename the nbh to RUU_Signed.nbh.
Also, if you are a carrier other than Alltel, you will need to install the proper carrier cab for your provider. You can pick that up from here:
http://dcd1182.n715dp.com/titan/carriers/
Hope that helps!
Ivan
So does this rom that I got at the beginning of this thread have the radio included? If not, which should I get and from where...
I read that thread you sent me to but theres alot of information that just makes me confused.
I have an alltel ppc6800 with WM 6.1 stock. I only want the rom with 6.5 that I found in this thread.
Im not sure what chef is or a kitchen, except for the obvious...
ouellettesr said:
So does this rom that I got at the beginning of this thread have the radio included? If not, which should I get and from where...
I read that thread you sent me to but theres alot of information that just makes me confused.
I have an alltel ppc6800 with WM 6.1 stock. I only want the rom with 6.5 that I found in this thread.
Im not sure what chef is or a kitchen, except for the obvious...
Click to expand...
Click to collapse
First, a "kitchen" is a program used to create ROMs. A "chef" is a person such as myself who uses the kitchen to create ROMs.
Second, custom ROMs do not contain radios. Make sure you have a 3.x radio. Personally, I use the 3.42.50 (the latet radio made available for our phones). You can check your radio version in Start -> Settings -> System -> Device Information. If you need to upgrade your radio, go here and download the latest Alltel ROM (which does contain the radio):
http://www.htc.com/us/SupportDownload.aspx?p_id=63&cat=2&dl_id=114
You will need to re-unlock your phone afterwards.
Third, make sure you understand everything on that wiki I sent. It is extremely important that you understand what you are doing to your phone when you unlock/upgrade. There is the potential for this to either go great and you will be very happy...or for this to not work out well at all and damage your phone if you make mistakes. I'll do what I can to help explain things, but we need to make sure you understand.
Here is another important page to read:
http://wiki.xda-developers.com/index.php?pagename=TitanForBeginners
Also, please note that you will lose all of the data on your phone. Make sure you backup any contacts, calendar items, etc by using available programs. I prefer PimBackup (http://www.dotfred.net/). Also, make sure you have any cabs you may need to re-install your desired programs after upgrading.
I started the Bootloader update utility and now im stuck at the tri-colored screen. it says SPL-2.40.Olipro CPLD-9 the dos window dissapeared at this point...
I read somewhere I need to disable activesyne and run a program ~ http://forum.ppcgeeks.com/showthread.php?t=9229 ~ and that should take care of it but i cant figure out how to disable activesync in vista.
Uh oh....
ouellettesr said:
I started the Bootloader update utility and now im stuck at the tri-colored screen. it says SPL-2.40.Olipro CPLD-9 the dos window dissapeared at this point...
I read somewhere I need to disable activesyne and run a program ~ http://forum.ppcgeeks.com/showthread.php?t=9229 ~ and that should take care of it but i cant figure out how to disable activesync in vista.
Uh oh....
Click to expand...
Click to collapse
That SPL means your phone is unlocked. Congratulations. Now flash the radio (if necessary) or the new ROM. You're on the right track! And don't disable activesync.
Edit - Vista doesn't even have ActiveSync. We Vista users have Windows Mobile Device Center.
I cant get it to go past the tri colored screen though...
I haven't updated my bootloader in almost a year, so I'm a little rusty. But here are a few things to try:
If you are flashing from the USB, take out your SD card. If you are flashing from SD card, take out the USB cord. It's preferable to flash via SD card if you have one that is compatible.
If that doesn't work, what happens when you try to run the exit bootloader program from the thread you linked?
Ok, I figured it out thanks to you. It was just waiting for the new Rom..
Thanks for your help..