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
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?
Simple steps on howto
1. download the kitchen Download
2. download Prophet Touch X rom Get it here
3. extract Kitchen and Prophet Touch X to separate folder
4. Place the OS.nb from Prophet Touch X in the rom folder of the Kitchen
5. run Buildos.exe and choose what to include (the marked apps are the once that are in Prophet Touch X) press the green play button and wait for it to finish
6. run CreateROM.bat (if there is any error the you have included to much in the Buldos prosess)
7. if there were no error the new OS.nb is in the temp folder move it to the Prophet Touch X folder and overwrite the os.nb in it
8. flash any step 1 WM5
9. now Flash your new rom within Prophet Touch X folder
if everything is done right you should have your new coocked rom on your Prophet
I have put all the things that should not be removed into the SYS folder so do only make changes to the OEM folder till you know more about cooking .
replace the HTC Audio Manager with this one
View attachment OEMAudioManager.zip
New HTC Album with folder option
View attachment HTCAlbumFolderOption.zip
Extras and links
I'll upload some addons for the kitchen later on as I've made more OEM packs
You can also search for oempacks to include but be aware that some OEM packs are device depented
Some cool tools that I use but have not included in kitchen You'll need to understand what they do before using them
HyperCore Kitchen cool for dumping roms and building ( I use it for dumping)
this is great.. awesome.
Great job Gullum. Now guys, we all should start frying Hokienmee or Char Kueh Teow (both chinese cuisine)
geney said:
Great job Gullum. Now guys, we all should start frying Hokienmee or Char Kueh Teow (both chinese cuisine)
Click to expand...
Click to collapse
I like both of them..LOL..
Really love this kitchen...
Thanks man, you are great!!!
It'll be even better if have a list of what those things really for. I do not know which box to check and which one is not
Maybe I'm too new for 'cooking'
geney said:
It'll be even better if have a list of what those things really for. I do not know which box to check and which one is not
Maybe I'm too new for 'cooking'
Click to expand...
Click to collapse
hold the mouse over one of the options and there should show and explaination for most of the items
good news
i'll try it
for every change in X and flashing it, is it always necessary to do step 1 again (wm5 flashing) ?
When I do hard reset and at the "tap screen to go on" point, I could start flashing X too ?
What I mean, is the complete rom exchanged when I flash X, or do some parts from wm5 or old X (IX, VIII ....) remain ?
I've try to cook today.. BUt seems something is going wrong...
Better I flashed it back to the original touch X ROM...
I also had some bad luck with cooking.
I did everything gullum said, flashed 'new' TouchX, did hard reset and then when its time to see welcome screen and 'press any key.....' there is blank white screen! Nothing happens no matter which button i press! Any ideas?
mcupurdija said:
I also had some bad luck with cooking.
I did everything gullum said, flashed 'new' TouchX, did hard reset and then when its time to see welcome screen and 'press any key.....' there is blank white screen! Nothing happens no matter which button i press! Any ideas?
Click to expand...
Click to collapse
I did the same think.
At my case, i have enter today screen.. But I think, its programs don't install clearly.. (hard reset don't help either.)
The first screen is the same one as you.. The white one.. Maybe you should to try ask Gullum again..
I just flash back to Touch IX with another Ext ROM. QuickMenu in that ext.ROM
thanks gullum
I would like to translate this rom to Portuguese can you give some advices? our some tutorial to do that, please? can i do that with this soft?
best regards
thanks (for this perfect kitchen) gullum ,some 3 questions i have :
1.>how to get oem or make one ,and
2.>how to get .dsm , .rgu files of my favorite software . and
3.>how do i make registry changes prior to build os are they automatic
Note :ext_rom files attributes should be read only since its like that in original rom so i made them read only(i think its healthy for system files any virus won't be able to modify it unless the file needs to be appendable updateable it should be read only),plus i deleted alot of thumbs.db files lying in many folders (about >2mb) just to clean oem folder files off thumbs.db i know winxp might be making them all the way .
i corrected audio manger with this kitchen (its gr8),i can't seem to solve camera album (have solved solution given below )problem ,it seems to have come back you know i can't use gestures , what to do ,any reg setting solution.
Edit : **corrected** the setting in reg hklm\software\htc\htcalbum\cacheserial to 2130706432
and hklm\software\htc\htcalbum\default_viewer to 0
if it still don't get solved set first 11 enteries (h_enable to v_pos) value to 0 in
hklm\software\htc\htcalbum\touchscroll\htcalbumclass
i'll try to provide a cab but this forum has alot of intelligent members
BuildImgfs
whatever I include in the buildos I am facing the same error when I try to create rom; something about BuildImgfs
any help guys!!
ma3ayta said:
whatever I include in the buildos I am facing the same error when I try to create rom; something about BuildImgfs
any help guys!!
Click to expand...
Click to collapse
2 reasons 1.> i hope you are pressing play(top left in build OS)button after whatever you choose,with what ever you want in it.
2.>your file size has to be limited its almost full with this kitchen so you have to remove some item like voice dialing (which i seldom use) or some other item removed before you add some item since size dependency is very important here ,and later run create rom .remember you cannot select everything because of space limitation .
Hello Gullum
I'm trying to do very basic thing adding Windows Live package into the OS.nb but it fails during CreatROM.bat. At BuildImgfs.exe the application BuildImgfs.exe crashes and show the error message and whether to send a report to MS or not (I don't send...).
I just directly add Windows Live to your OS.nb. Is it already fully loaded? Should I remove something before?
question with task manager
something is wrong with task manager.
in control panel ,its setting doesn't work!
Same problem.
Whatever i select in buildOS, BuildImgfs crashes.
Last records is CreateROM.bat window is:
Processing "Painting.gif" as file
Processing "S5K3BAFX.dll" as file
Processing "3aca900a-0834-11dc-8314-0800200c9a66.dsm" as file
Processing "c7dbe475-1d17-4fbf-a63e-af6dc042569a.rgu" as file
Processing "c7dbe475-1d17-4fbf-a63e-af6dc042569a.dsm" as file
Processing "-жE+-A+?.txt" as file
I think reason in strange file name -жE+-A+?.txt.
BINGO!!!
I Found this file in Prophet Touch kitchen.
\\OEM\Quickmenu\-жE+-A+?.txt
Just delete it before kitching.
!This ROM is based on FireROM (0.3) by Chainfire!
Credit goes to him for making this ROm and being the first one to release a cooked Raphael ROM. He asked me to change the name of the ROM which I have done (needed to upload the whole stuf to rapidcrap again
The new name of the ROM will (for now) be Baaijte 0.1
After I mentioned my adjustments to the original FireROM in that thread, some people asked me to post this ROM, so here it is.
http://rapidshare.com/files/141632465/Baaijte01.rar.html
This is the very first time I've cooked a ROM. I'm running it on my own TP without problems, but that is the only testing it' has gotten. If you find things are not working as they should, I would really appreciate some feedback (be gentile though )
What have I changed:
-removed tcmpcp
-removed pocketrar
-removed wktask
-removed QickMenu
-restored LargeMenu and regular taskmanager
-altered weather locations to give stock NL list
-removed 4 icons-in-a-row adjustment
-replaced BCR with west european version
-added call history tab (extracted info from cab in diamond apps section)
-added googlemaps
-restored startup gif and wav
-t9 languages added (dutch anyway)
-removed PlayShow
-removed getting started video
-added ringtone Atmosphere (converted to wma and made it default)
-sliding sound (keyboard) on, set to 4 (Mechanical) (did not show up checked on restart though)
-Set identity to TouchPro
-Long end key press turns of data connection (not sure if this works)
-restored original splash, animation and sound
-altered list on internet tab to give stok NL list (google.nl, telegraaf, etc.)
I'm interested in updating the WM build to 20721 but don't know how to do that. If one of the more experienced chefs wants to explain, it would be much appreciated.
Yep, no idea what to say here except thanks for the work and after wiping the sleep from my eyes.......
"""""WM build to 20""7"""21"""""""""""
from 20273 to 20721 is an uprgade
Just flashed and running now! Thanks for the ROM.
If I discover any bugs I'll let you know.
I would appreciate it if you changed your ROM's name and state somewhere it's based on my FireROM instead. When I continue cooking my own ROMs, I will want to use the FireROM name again.
heheh, I wiped the sleep from my eyes to discover that too
Xtreme XL said:
from 20273 to 20721 is an uprgade
Click to expand...
Click to collapse
Your wish...
Chainfire said:
I would appreciate it if you changed your ROM's name and state somewhere it's based on my FireROM instead. When I continue cooking my own ROMs, I will want to use the FireROM name again.
Click to expand...
Click to collapse
...is my command
Had no intention to hyjack the name. Used it so others could guess what is was about. Will change the name. See announcement in first post. As I said in th PM: If it troubles you, I'll remove it.
Good day,
I am trying to update my pro (tmobile) with your rom.
I did a hardspl and conformed it at the manual bootloader.
but everytime i run the romupdateutiliy my phone goes black.
the status bar is on my pc screen (vista) and nothing happens for about 2 minuts.
then it says it is failed.
What am i doing wrong ?
never had this issue with my Diamond.
flashed it this morning the same way i am trying to flash the pro.
anyone??
anheuer said:
Good day,
I am trying to update my pro (tmobile) with your rom.
I did a hardspl and conformed it at the manual bootloader.
but everytime i run the romupdateutiliy my phone goes black.
the status bar is on my pc screen (vista) and nothing happens for about 2 minuts.
then it says it is failed.
What am i doing wrong ?
never had this issue with my Diamond.
flashed it this morning the same way i am trying to flash the pro.
anyone??
Click to expand...
Click to collapse
Soory, don't know what is wrong. Mine is working fine with this ROM.
anheuer said:
then it says it is failed.
Click to expand...
Click to collapse
Do you get an ERROR code? And if yes... which one?
I've added your ROM to the Cooked ROM's wiki page.
I've installed it, works great! just one thing allready noticing:
i can't seem to select other wifi data encryption modes other then WEP.
SO i can't connect to my WPA router/modem. Previously i was running
RAPH300
APL-1.69.0000
MicroP-Herm (LED) v13
MicroP-Herm KEY v8
Psoc-herm stage_cvt v0x35
BRanded dutch t-mobile mda, and i had more wifi settings.
Iss there maybe a .cab or something i can download to patch the wifi ?
Never mind, above issue was only when i had the USB cable detected, and therefor it probably uses shared internetthrough my PC and cant use wifi, unless its sharing or something?
I did have some issue's with the keyboard lagging/not responding at all in certain things, but i had it soft reset and everything si working very smooth!
how do i flash the rom with hardspl, shall i overwrite the RUU_Signed.nbh with the downlaoded one in the hardspl folder. pls help
Thanks
WatskeBart said:
I've added your ROM to the Cooked ROM's wiki page.
Click to expand...
Click to collapse
Had not thought about that yet. Was thinking that it only applied for real chefs
sluden said:
how do i flash the rom with hardspl, shall i overwrite the RUU_Signed.nbh with the downlaoded one in the hardspl folder. pls help
Click to expand...
Click to collapse
Indeed you need to have the custom RUU upadter (the .exe) and the .nbh in the same dir. Just run the exe and folow the steps.
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.
ok....
here's the deal:
I've been using an OEM-package in mylast roms for tomtom version 7.915.
This has been working without troubles.
Now I cooked a new ROM based on new 21018 XIP/SYS
The device really flies and everything seems to working flawless....EXCEPT tomtom.
When I start Tomtom, in a flash I see the gray bootscreen but then immediately I get the error: 'Unable to start. Not enough memory is available.'
But I have more then 130mb program memory available so that can not be the issue....
I did not change anything to the OEM-package. So I guess it has something to do with the new SYS.
Do more people have this problem and/or does somebody now the fix....
Thnx all in advance for your help!!
Greetz Merten
p.s. I used the search function of course and saw a lot of similar errors but no sollutions.....
I am running TomTom 7.915.9196 (OK via a cab) on 21028.1.6.0 (just installed yesterday)
This is Da_G's simple kitchen plus the updated pack posted in that thread this morning.
Don't know if that helps, but I would be very interested in an OEM for TOMTOM if you can get it working?
crazyC said:
I am running TomTom 7.915.9196 (OK via a cab) on 21028.1.6.0 (just installed yesterday)
This is Da_G's simple kitchen plus the updated pack posted in that thread this morning.
Don't know if that helps, but I would be very interested in an OEM for TOMTOM if you can get it working?
Click to expand...
Click to collapse
I got the exact same oem-package working in M-rom v1.71!
So it really beats me why I get the error.
I tried cooking the rom again but still the error....
I am still cooking up my rom and so will reflash tonight - if you can post up your tomtom OEM I will take a look and try and flash it and see if I can get it to work? Maybe a conflict somewhere that might not be on mine as I do chaneg a number of the packages.
crazyC said:
I am still cooking up my rom and so will reflash tonight - if you can post up your tomtom OEM I will take a look and try and flash it and see if I can get it to work? Maybe a conflict somewhere that might not be on mine as I do chaneg a number of the packages.
Click to expand...
Click to collapse
Ok OEM can be found here in the map: packages
Package looks OK at first glance - hope to be able to try it tonight and will post back tomorrow with results.
If this doesn't work - you could try simply using the cab via UC etc as I do - I have checked and the cab of the same version in your OEM DOES work for me.
In fact, I think I might leave it in my UC, (but will flash tonight anyway with it just to see)
merten3000 said:
When I start Tomtom, in a flash I see the gray bootscreen but then immediately I get the error: 'Unable to start. Not enough memory is available.'
But I have more then 130mb program memory available so that can not be the issue....
Click to expand...
Click to collapse
I had the same problem some time ago, and it turned out to be SKtools automated Free-Ram shadow service that was causing this.
You dont happen to have similar software running (something that clears your RAM on the fly)?
GenghisZ said:
I had the same problem some time ago, and it turned out to be SKtools automated Free-Ram shadow service that was causing this.
You dont happen to have similar software running (something that clears your RAM on the fly)?
Click to expand...
Click to collapse
I tried new ervius packagetool: 5.3 and saw something about shadow service... will roll back to 4.3b1 and see if tool is the problem...
Thnx for the tip!
merten3000 said:
I tried new ervius packagetool: 5.3 and saw something about shadow service... will roll back to 4.3b1 and see if tool is the problem...
Thnx for the tip!
Click to expand...
Click to collapse
Nope, did not help...
OK - apart from the shortcut not being copied to programs - I didn't check the initflashfiles first - d'oh - it works.
I went to windows with file explorer and ran it from there - no problems.
Have flashed twice - it must be something else in your rom.
Does the page pool make any difference? or the filecache sizes?
crazyC said:
OK - apart from the shortcut not being copied to programs - I didn't check the initflashfiles first - d'oh - it works.
I went to windows with file explorer and ran it from there - no problems.
Have flashed twice - it must be something else in your rom.
Does the page pool make any difference? or the filecache sizes?
Click to expand...
Click to collapse
I always change my roms pp to 32mb...can that make a difference? I did it in v1.71 and tomtom worked fine...
I don't know - I have been around here long enough to know that your skills far outweigh mine. If it used to work then I see no reason for the change.
All I know is that my rom is based on Da_Gs really clean latest (ie 5.08) from his simple kitchen thread (from his post near the end not the first post) plus Eras2rs package updates.
The only other packages I add are a few utilities and personal tweaks. I import an advanced config xml as part of the UC process but that just ensures the various settings in Advanced Config are set to advised etc.
Hi,
I don't know if this can help but I got this same error message when the map isn't correctly activated.
Regards,
___________
TP - RomeOS 1.70
Harikoss said:
Hi,
I don't know if this can help but I got this same error message when the map isn't correctly activated.
Regards,
___________
TP - RomeOS 1.70
Click to expand...
Click to collapse
Maps work(ed) fine..
btw I bypassed the error by removing the OEM-package and made it a cab which is installed during system configuration. It takes more system space but this way it is uninstallable....but it remains a mistery to me why the OEM does not work in this SYS and does in 21014 SYS...