Related
DCD if you dont like what im doing just tell me to delete this post and i will.
All credit goes to DCD one of the best kitchen and Rom maker's out there.
If it wasn't for him our 6800's would be almost useless.
This is for the people who are using the titan kitchen. I took DCD's latest build and repackaged it for the PPCKitchen.org Titan Kitchen located
here http://forum.ppcgeeks.com/showthread.php?t=23206
Place it in your BuildOS/Kitchens directory and then extract "Titan_DCD_3.01_Selections.txt" and place it in the BuildOS/Projects directory.
Now you can create your own custom DCD rom using the new kitchen and DCD's latest build.
I've been using this for about 20 hrs and the rom is very stable.
Thanks again DCD u Da MAN!!!!!!!!
Make Sure to remove---> _fixed <---from the end of the file before u place it in the kitchens folder.
Download
http://rapidshare.com/files/108106961/Titan_DCD_3.0.4_FIXED.rar REALLY FIXED this time LOL
thank i'm looking for this. I ran into error error nk.dat
AstronusX said:
thank i'm looking for this. I ran into error error nk.dat
Click to expand...
Click to collapse
Sorry i forgot to change it from os.paylod to nk.fat, im up loading a fix right now thanks.
Errors in PPCkitchen
King - Thanks for putting this together
Unfortunately, I'm getting an error message (a bunch).
I downloaded the main file and did the updater.
When I go into BuildOS and select DCD 3.0.4 5054 or 5060, I am bombarded with error messages "Internal Error - Option.xml GUID not found (PROGRAM - xxxxxxxxxxxxxxxxxxxxx) where the "Program" is the name of the program and the x's are registry keys.
After I click ok 100 times to get through to the Kitchen, it allows me to select programs and build the OS, but once I install it, nothing actually gets installed on the phone.
Do you know what is causing this? Any help would be appreciated.
Thanks,
mfrish said:
King - Thanks for putting this together
Unfortunately, I'm getting an error message (a bunch).
I downloaded the main file and did the updater.
When I go into BuildOS and select DCD 3.0.4 5054 or 5060, I am bombarded with error messages "Internal Error - Option.xml GUID not found (PROGRAM - xxxxxxxxxxxxxxxxxxxxx) where the "Program" is the name of the program and the x's are registry keys.
After I click ok 100 times to get through to the Kitchen, it allows me to select programs and build the OS, but once I install it, nothing actually gets installed on the phone.
Do you know what is causing this? Any help would be appreciated.
Thanks,
Click to expand...
Click to collapse
Is this your first time using the kitchen?
King_tee - I had to do alot of editing to get ALL the errors to go away. I had to remove the welcomehead96.png, also had to remove a few other items.... like remotedesktop..... I guess I should have taken a log of what I did....
Edit - However - VERY nice job getting it to where it is..... Thank you
Thanks will try. The BuildOS in the regular kitchen is crashing so I can now cook a kitchen.
Also will my OEMs made for the 3.0.1 rom work if I put them in the build os directory. I didn't use the OEMizer w/ BuildOS. It appears to be the same just w/ a different save directory.
azclown said:
King_tee - I had to do alot of editing to get ALL the errors to go away. I had to remove the welcomehead96.png, also had to remove a few other items.... like remotedesktop..... I guess I should have taken a log of what I did....
Edit - However - VERY nice job getting it to where it is..... Thank you
Click to expand...
Click to collapse
No prob az i forgot about getting rid of those files. I thought i got all of them. I will upload a new file with the fixes for those who haven't downloaded it yet.
NEW FILE UP LOADED
Let me know if its working for you guys
As of this morning, the version I downloaded still gives an error (can't find HTC Sliding Sound module) when trying to load the selections.txt file for the DCD kitchen.
drgreenberg said:
As of this morning, the version I downloaded still gives an error (can't find HTC Sliding Sound module) when trying to load the selections.txt file for the DCD kitchen.
Click to expand...
Click to collapse
The sliding sounds module is in the DCD OEM's folder......when u open it up in the kitchen it should come up as a selectable OEM. At then point all you have to do is select it.
Bell?
Does the kitchen work for Bell phones? It does not seem to be in the carrier list.
jondixon said:
Does the kitchen work for Bell phones? It does not seem to be in the carrier list.
Click to expand...
Click to collapse
I don't know if it does.Are you are referring to the ppckitchen or DCD's Kitchen?
What i have provided is just a modified version of DCD's work (all credit goes to him) that will work in the ppckitchen.
You can check over here http://forum.ppcgeeks.com/showthread.php?t=23206
if you are talking about the ppckitchen, and they should be able to answer your questions.
If you asking about the DCD kitchen you can ask over here http://forum.xda-developers.com/showthread.php?t=385336 and im sure he will help you out.
I guess the obvious question is, what's the difference between the two kitchens?
DCD's kitchen is built around his ROM. The PPCkitchen kitchen isn't designed for any specific ROM or device.
Advantages of DCD's kitchen:
It's what DCD is using, so you know it builds his ROM like he intended it.
Advantages of PPCkitchen's kitchen:
Easy to install.
Prettier front end.
More error checking.
More OEMs to pick from.
Self updating.
Device dependency/exclusions supported
Carrier dependency/exclusions supported
OEM dependency/exclusions supported
Easy to move same configuration from one kitchen to the next.
Effortless switching between ROM configurations and kitchens
Splash/animation support
gguruusa said:
DCD's kitchen is built around his ROM. The PPCkitchen kitchen isn't designed for any specific ROM or device.
Advantages of DCD's kitchen:
It's what DCD is using, so you know it builds his ROM like he intended it.
Advantages of PPCkitchen's kitchen:
Easy to install.
Prettier front end.
More error checking.
More OEMs to pick from.
Self updating.
Device dependency/exclusions supported
Carrier dependency/exclusions supported
OEM dependency/exclusions supported
Easy to move same configuration from one kitchen to the next.
Effortless switching between ROM configurations and kitchens
Splash/animation support
Click to expand...
Click to collapse
I honestly don't think you give DCD enough credit for his work.... Here are some more Advantages....
Easy to use
Builds a basic ROM with only 2 clicks of the mouse.
Can be used behind firewalls.
No IP logging when you use it. (I had been told this was logged with your login name)
In all fairness both systems work very well, while the PPC kitchen has a more elegant streamlined interface, I do believe the end result is the same, a working ROM the way "I" want it.
error
hey guy anybody else getting an error unable to make file
when it goes to unpack the ppcgeeksoem rar
azclown said:
I honestly don't think you give DCD enough credit for his work.... Here are some more Advantages....
Easy to use
Builds a basic ROM with only 2 clicks of the mouse.
Can be used behind firewalls.
No IP logging when you use it. (I had been told this was logged with your login name)
In all fairness both systems work very well, while the PPC kitchen has a more elegant streamlined interface, I do believe the end result is the same, a working ROM the way "I" want it.
Click to expand...
Click to collapse
Could be because DCD has only a little to do with what we're talking about (which I gave him credit for). That's Bepe's buildos you're looking at, and essentially what we're comparing is Bepe's buildos w/ DCD integrated against PPCKitchen's buildos w/ DCD integrated.
You can't seriously suggest that Bepe's buildos is easier to use - the interface is practically identical! Both are about the same difficulty to use in their most basic, unaltered configurations, and both can build a basic rom w/ 2 clicks. Installing, configuring, starting, and maintaining is a lot different however...the nod hands down goes to ppckitchen there. Once you get past a basic configuration, PPCkitchen's buildos is unchallenged.
The proxy/firewall thing is fixed (general release this weekend) and it doesn't log IPs (never has).
Bepe's buildos get's the nod for no internet connection required, and the previous version (I don't know about v2) get's the nod for Linux compatible. Bepe's buildos also get's the nod for being more interfaceable to other projects and having more projects using it, but none of that is related to the original question (except maybe linux compatibility). [EDIT: v2 isn't native linux compatible, so no nod there.]
All of this is not too suprising, as PPCkitchen's buildos is, at it's core, an evolution of Bepe's Buildos.
I give credit to all sources DCD's kitchen / PPC Geeks kitchen and more.
They both offer the tools to make a ROM to your likings, some better then other, but the fact of the matter is that it gets the job done.
What PPC Geeks version is doing is making a bit more user friendly ( in my opinion ), but I still used DCD's kitchens because I really don't add any extra OEM's to my ROM's unless it is a specifically Themed ROM and then again I can get it done with both kitchens with ease.
I guess users will just have to test them both out themselves to see if they prefer one or the other.
What would be great is if we can have a Modifier / virtual simulator / kitchen where we can find ways to modify our ROM's / PPC's to their best potential ( such as drivers, RAM Management that works / compatibility with different OS and maybe interface change support ).
A virtual simulator to test out all of our modifications by simulating our respective device just as if we were to cook the ROM ( this could save tons of time rather then just flashing all the time or preventing an accidental bricking of your phone)
And a Universal kitchen for practically any Device ( well TITAN at least for our use ) that works on XP, Vista, MAC, and even Linux.
Im sure with all the developers on this forum and on ppcgeeks we would be able to get this done some time in the future.
Just an Idea....
[email protected]$ said:
What would be great is if we can have a Modifier / virtual simulator / kitchen where we can find ways to modify our ROM's / PPC's to their best potential ( such as drivers, RAM Management that works / compatibility with different OS and maybe interface change support ).
A virtual simulator to test out all of our modifications by simulating our respective device just as if we were to cook the ROM ( this could save tons of time rather then just flashing all the time or preventing an accidental bricking of your phone)
And a Universal kitchen for practically any Device ( well TITAN at least for our use ) that works on XP, Vista, MAC, and even Linux.
Click to expand...
Click to collapse
PPCkitchen buildos is actually the closest you can come currently for easily swapping components around, and there's a universal kitchen here on xda that supports many devices (way more devices than PPCkitchen does).
Don't hold your breath on the hardware emulator
lightbiter said:
hey guy anybody else getting an error unable to make file
when it goes to unpack the ppcgeeksoem rar
Click to expand...
Click to collapse
You'll have to elaborate a little better. If I had to guess, however, I'd say that you might have an older version of winrar installed. As a workaround, you can manually extract and modify the selections to use the extracted dir instead of the .rar.
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.
Note for Mods: If you feel that this thread belongs to some different forum, feel free to move it (coz i also have this feeling, but i am not clear
Hi Friends,
I have seen this discussion many times that the older GReloc cannot be used for relocating newer, WM 6.5 SYS. While this is partially true, there is a workaround for this that I have been using with last 2-3 WM 6.5 ROMs that i have cooked for myself. So i thought it will be good for all the fellow chefs and wannabes if i share this info with you.
Although the new tool WMReloc can be used in place of GReloc, i don't find it as user friendly as GReloc and since GReloc works for me, there is not enough reason for me to switch over. Also, once or twice i have seen reports of WMReloc doing overlapping of addresses while the relocation process which defy its sole purpose.
So here is the method I use :
1. Download Unlocker from Here. This will help you unlock files that are currently in use by other programs so that you can copy move and delete them. Install it and on every file and folder you'll get a new entry in context menu called "Unlocker".
2. Now start Greloc.exe and fill in proper values if needed. Click "Do It". When it gives Integer Overflow, click OK but dont close it. Press "Do It" again and this time it will show you the file that is givin error in the message box, mostly its a .tmp file.
3. Go to the file, right click on it and select "Unlocker". In the box that opens, on the right hand, choose delete in the dropdown box. Now click Unlock All. This will delete the file.
4. Click "Do It" in GReloc Window again, this time it will complete the process. If the error comes again, for a different file (never happened with me though), repeat this process.
5. To be sure, run GReloc once again and it will complete the process successfully in one go.
Explanation:
Although I don't claim to be an expert on this subject, As far as my understanding goes, the problem lies within the algorithm used in GReloc. It uses integer data typed variables for doing whatever it does during the relocation process and with Wm 6.5, somehow the value stored in one of these variables crosses the upper or lower limit of the allowed range for integer variables.
Now, In the process of relocation, GReloc creates a tmp file based on the contents of the modules it is relocating. When error occurs GReloc stops as it is and doesn't closes the handle to this tmp file. This causes the process of relocation to fail on successive attempts.
What we do is we unlock this file forcefully using unlocker and delete it. This way, GReloc restarts the relocation process from that module again and the problem is solved.
Happy Cooking!
Hi sumit,
Great tutorial. It'll be aplicable not only to wm6.5 but to wm6.1 as well. In some wm6.1 roms i have the same problems.
this is temporally solution if u want to know how to use wmreloc i will tell u
but if you r using ramersonw kitchen it will little bit trick becoz tool folder comes when you start kitchen
i have my own kitchen witch support wmreloc 1.4
@ ramersonw
if u want to add wmreloc support to your kitchen contact me , and what about your visual kitchen ? is it done ? tell me if you want any help .
@Ankit: Yes its a temporary solution, it was working for me for last few roms so i thought it may be of some use to others also. And Yes, Please post the tutorial for using WMReloc.exe either in this thread (I'll rename the title of thread in that case) or in a separate thread, as you find it appropriate. That will be really good. Try to post the necessary tools with it too, like the WMReloc.exe file itself and anyother thing needed to use it.
In Ramerson's kitchen, the tools folder is created at start of the process, and buildos runs for atleast a minute or two, so the files in tools folder can be replaced in that period.
@Ramerson: Ya, the problem can occur in WM 6.1 also. I think it has to do something with the number of files that GReloc is relocating. Actually at the start of the relocation process, GReloc seems to be calculating which files needs to be relocated, and if this number exceeds a certain limit, that i am not aware of yet, it crashes. But when the relocation process is resumed from the point of error, number of files to relocate comes within the range and then GReloc continues. Great thing is that GReloc is a .NET app and exception handling has been done quiet intuitively otherwise there was no chance to resume this process.
Anyways Buddy, These are just assumptions and are working for now but this may not last for long so i think its really the time to update your kitchen. I request you to either you do it, or please share the code with me and i will try to understand and port it to .NET for further development.
krazy_about_technology, hi, put that in the attache a folder tools in their kitchen. And replacement following -" GReloc-doit-dump" on - "start / w "" tools \ WMReloc.exe-g. \ Temp \ dump-lWMReloclog2.txt"
Good luck
@ankit
this is temporally solution if u want to know how to use wmreloc i will tell u
but if you r using ramersonw kitchen it will little bit trick becoz tool folder comes when you start kitchen
i have my own kitchen witch support wmreloc 1.4
Click to expand...
Click to collapse
can u upload ur kitchen for wm6 & 6.5 plz ............
ankit360 said:
this is temporally solution if u want to know how to use wmreloc i will tell u
Click to expand...
Click to collapse
Please can you write tutorial on this?
In my case g'reloc missing S001 file, iam forget which module, so i use wmreloc, it was working well.
Xumit said:
Please can you write tutorial on this?
Click to expand...
Click to collapse
change
G'Reloc -doit -dump
with
wmreloc -gtemp\dump
swapnil_0081 said:
@ankit
can u upload ur kitchen for wm6 & 6.5 plz ............
Click to expand...
Click to collapse
You can download ankit wm6.5 kitchen, edit file build.cmd in the tools folder,
find line
start /w "" Tools\G'Reloc -doit -dump
change it with
start /w "" tools\wmreloc -gtemp\dump
save the file.
copy wmrelox.exe to tools folder
The file missing is in either marketplace or my phone. I got that message too. I removed these two packages and thereafter the process went smoothly. WMReloc skippes these files. Did you checked whether these services are working in your wmreloced rom?
I can't found it in wmreloc log, but it work well in my gene
I will give you solution very soon
http://www.htc.com/www/SupportDownload.aspx?p_id=133&cat=0&dl_id=538
It's for the Diamond, but assuming it works on the Raph, Da_G, can you work your magic and integrate whatever's needed from here into your kitchen(s)?
OEM_Misc.dll
Extracted Diamond_audioplayback.exe contents, verified _Setup.xml, Platformxxx.reg and CM_Entries.xml:
- No registry changes
- Attached file is copied to .\Windows folder on device
Place file in .\OEM\OEMDrivers if cooking in kitchen.
Cheers,
Thanks -- trying it in my own ROM now ...
hilaireg is way ahead of me
ill check it out when i get home from the hospital! sounds good
Super-newbie question: What did you use to extract it from the EXE?
@Da_G:
Figured your queue was full enough as it is
@Wordsmith9091:
I used WinRAR 3.3 (IZArc 3.81 couldn't open the .EXE). Once it was extracted, I had a look at _setup.XML as it contains the short-to-long filename conversion details.
I renamed the pertinent files (previous post) and had a look at the content in those to ensure that there were no special requirements.
I used IZArc 3.81 to .ZIP up the file so that it could be posted here.
Thanks -- I learn a new trick every time I come to this site
Just tried building my ROM with it, all seems well so far, though I havne't played enough audio to test yet ...
... but I lost the ability to set button assignments other than Button-1-hold in the buttons panel -- it's like the stock behavior. Is that also controlled by this DLL?
Edit: Never mind, I'm a moron, this issue had nothing to do with this DLL
I don't think so ... the Stock HTC ROM only included "Button 1" which drives me crazy.
I've got a task on my list to deal with that I soon as I'm done some other kitchen related stuff.
I'll post up - unless someone beats me to it - once I figure out how to get button mapping.
Cheers,
I can't be 100 percent sure it's what interfered with button mapping, but it's the only thing I can think of that i've done different between builds.
Since this fix only requires a single DLL copied to the \Windows folder, I was able to cab it up using ChainFire's DriverWiz tool, and install it. I stream music via A2DP during every car ride, so I'll be able to test this on my ride home. I'll attach the cab if anyone else wants to try it as well.
You make me proud Captain
Following your lead, I have attached a .ZIP that can be used in a kitchen; to use:
Extract the .ZIP to the PACKAGES folder.
Verify that the <GUID>'s on the .DSM don't collide with ones you are currently using.
Remove the OEM_MISC.DLL from the .\OEM\OEMDrivers folder.
Cook away.
Note:
Tested on Da_G's (ERAS2R/Me) 21042 kitchen.
HTH,
HTC Diamond Hotfix..
Many thanks Captain_Throwback for the CAB, am testing Music Player now. The HTC version will not install on the Orange Diamond says 'Not Compatible'.
... 25mins in..clean as a whistle!!
....3 albums in, job done.
Never mind on the button-mapping question. I realize what I did (I think). HAd nothing to do with this dll.
Any info you can pass my way?
hilaireg -- PMed you.
Well, I drove around for a bit after cooking this in and reflashing, and I still got some skips listening to music in Kinoma Play. Don't know if that's Kinoma's fault or if it's a symptom of the problem this is meant to address. I wasn't getting any skipping with the TF3D player even before applying this.
improvement?
I saw a noticeable improvement in the length of pauses in between my songs while streaming over A2DP (though it did get stuck on me after about 20 minutes). Its better than it was . . . I think. I don't know if there's really a scientific way to test this, really. Maybe the problem this is supposed to address isn't that at all. Maybe we need to find someone who actually KNOWS they have this problem, so we can see if the fix really helps.
Hotfix for Diamond..
I have a Diamond on the Orange Network with the stock HTC 1.93 ROM. It used to skip every 5 mins but after installing your CAB it is now perfect, not a glitch. I am a very happy bunny. Thanks for your work Captain..
looby said:
I have a Diamond on the Orange Network with the stock HTC 1.93 ROM. It used to skip every 5 mins but after installing your CAB it is now perfect, not a glitch. I am a very happy bunny. Thanks for your work Captain..
Click to expand...
Click to collapse
All I did was make the cab. Wordsmith found it, and hilaireg extracted it. Its a team effort. That's what a community is all about .
Captain_Throwback said:
All I did was make the cab. Wordsmith found it, and hilaireg extracted it. Its a team effort. That's what a community is all about .
Click to expand...
Click to collapse
And if he has a diamond, he could probably just install the hotfix directly from HTC
Wordsmith9091 said:
And if he has a diamond, he could probably just install the hotfix directly from HTC
Click to expand...
Click to collapse
He already tried that . . .
looby said:
Many thanks Captain_Throwback for the CAB, am testing Music Player now. The HTC version will not install on the Orange Diamond says 'Not Compatible'.
Click to expand...
Click to collapse
Hi all; I am new (here that is) but am fully capable microsoft certified & mvp coder.
Who is or want's to be or can help working on magldr compatible wp7 Kitchen and initial live-activated dwi rom?
1st goal here to make a kitchen then for hello_world just rebuild leo70 with live activated. Maybe get together here and setup proper dedicated irc. This may not be normal way to go about but I am not interested in social netiquette distractions. Just want to work on this and get it done. I have been using dumps (both my own and this: http://forum.xda-developers.com/showthread.php?t=915978 ) along with jtag, and everything at my disposal.
I am doing this now with progress already made and have been working on this since prior to leo70 public release.
if interested or have news or info please post here or pm me- thanks.
G-ThGraf said:
Could we make a WP7 ROM with Chevronwp7 and all tweaks i cooked in?
Click to expand...
Click to collapse
I am hoping to and trying to and will make a kitchen and then this so soon: YES!
leo70 said:
Anyone made any moves on .rgu to .provxml to enable service mode on leo70?
REGEDIT4
[HKEY_LOCAL_MACHINE\System\BootLauncher]
"Default"="ServiceApp.exe"
or:
REGEDIT4
[HKEY_LOCAL_MACHINE\Drivers\USB\FunctionDrivers\TFTP]
"DeviceName"="USBFNS3:"
"USB_MaxPower"=dword:32
"bcdDevice"=dword:00000000
"Product"="Generic Serial"
"idProduct"=dword:00000629
"Manufacturer"="Generic Manufacturer"
"idVendor"=dword:0000045e
"IClass"="{CC5195AC-BA49-48a0-BE17-DF6D1B0173DD}"
"Flags"=dword:00000002
"Prefix"="FTP"
"Dll"="tftp.dll"
Anyone use trivial ftp for FUU? anyone called these DLLs or used/moded these keys?
also: per Da_G partition layout and comments for wp7 hard spl: for FFU/RUU: is it serial or usb/kitl/ethernet?
I think injecting a certificate into leo70 and rebuilding dump up will then allow an ffu to be flashed; debugging this then leads to a lot; hspl, kitchen, new roms.
Click to expand...
Click to collapse
Where is all the action/info !?
I wish you all the luck to make this a wonderful experience. Hope people with relevant knowledge and skills join you for this cause.
first there need to be some tools to be made , like Reloc , rebuild imgfs , maybe a platformbuilder like bepe did.
after that you could make a kitchen.
Da_G have posted some interesting information in WP7 Development & Hacking section
http://forum.xda-developers.com/showthread.php?t=649914
maybe this would also help to understand the structure of the (our DFT) rom.
Sounds good guys. Potentially integration of the android set up could be good bypassing the need to copy partitions across etc.
Wow ... good luck my friend
-------------------------------------
Sent via the XDA apptalk leo android
The imgfs rebuild with all modify is possible with tools here http://forum.xda-developers.com/showthread.php?t=685272
But a this time i don't find way to rebuild flash.store.bin (part04.bin = os.nb) content bin's:
LOGO
BLDR
NK
SLDR1
SLDR2
IMGFS
USER
...
Maybe the DFT wait to give the tool for community ??
;p
Good luck seems an excellent idea
netdrg said:
The imgfs rebuild with all modify is possible with tools here http://forum.xda-developers.com/showthread.php?t=685272
But a this time i don't find way to rebuild flash.store.bin (part04.bin = os.nb) content bin's:
LOGO
BLDR
NK
SLDR1
SLDR2
IMGFS
USER
...
Maybe the DFT wait to give the tool for community ??
;p
Click to expand...
Click to collapse
HazzBazz said:
Sounds good guys. Potentially integration of the android set up could be good bypassing the need to copy partitions across etc.
Click to expand...
Click to collapse
sandman01 said:
Da_G have posted some interesting information in WP7 Development & Hacking section
http://forum.xda-developers.com/showthread.php?t=649914
maybe this would also help to understand the structure of the (our DFT) rom.
Click to expand...
Click to collapse
ceesheim said:
first there need to be some tools to be made , like Reloc , rebuild imgfs , maybe a platformbuilder like bepe did.
after that you could make a kitchen.
Click to expand...
Click to collapse
Cool.
we can at least discuss it all here maybe: put all relevant info together.
I agree with u ceesheim, with tools required etc.
What about 7/CE platform builder though, modify, plus existing tools for imgfs etc? I was thinking also: for now anyway: just disassembling dwi.exe and figuring out all of the other partxx of this build which gets around non-wp7-spl. its a great hack and bears with it some interesting methods which may lead to other things.
I am really just exploring all options for now; any ideas, thoughts, discoveries? To be honest I am only reverse enginerring it all and have not yet tried to rebuild flash.store.bin (part04.bin = os.nb). Was going to try a few os.nb in there and just see response of magldr etc. Been lazy last few days lol.
But point is seems FUU/RUU and then Cotulla,DFT,Bepe' DWI give us two different paths to explore here!
What are exact known problems & current states on that: trying to do dump to (re)-build+flash?
I think that is where I will work - figure out other partxx.bin and magldr and disassemble dwi.exe to make flasher.
Thoughts?
ceesheim said:
this is used to dump it :
http://forum.xda-developers.com/showthread.php?t=884239
I think it was part 4 you had to rename to .nb and then open in this rom tool.
Click to expand...
Click to collapse
netdrg said:
i use the tools here http://forum.xda-developers.com/showthread.php?t=685272
For make this dump
Click to expand...
Click to collapse
ceesheim said:
only different is that the tools from da_g are command line .
the link I posted is more noob prove
I just tested it , rename part4.bin to part4.nb
then open romtools and click open ,go to the location where you stored part4.nb and click it and hit the button open
Click to expand...
Click to collapse
Yep, thanks guys.
I use them all depending on what I am doing. Da_G great: use all these tools 4 imgfs, xip, uldr, xph, etc and yeah - can get same for part04.nb to rie. What been discovered/worked out for other partxx.bin of 'myname' ? emul' wp7 spl etc opened, explored? Anyone know overall kitchen progress thus far? Hope wp7 kitchen ppl can get together more so and get this done!
leo70 said:
Ok.........
Anyone looked at rgu for serviceapp.exe or got anything on this? calls to DLL for Trivial FTP for FUU? Also: questions if any wouldnt mind:
anyway to tweak dwi.exe just like daf.exe and use switches like |ro| and other switches and set part layout size etc? originally thought could force magldr to convert-extract by putting other partxx.bins on part(0) user then do userdata dump to .img but layout! and prob it just dump in original .bin anyway? not quite sure how dwi places converts- containers, fs, etc?
What IS known about magldr, partxx.bin(s), dwi.exe?
Yeah, im being lazy, maybe too hopeful here on these ones, but worth asking. I will fully disassemble dwi.exe later on .
If problem with rebuild .nb/.nbh perhaps use another kitchen like zero or visual osbuilder with wm6 and just rename .nb to part04.bin to even see if it will load at all; debug this and watch this strap up; I might try this with stock os.nb made to fit to size. CRC?
it may fail totally but I want to see why and where/when/by what. ie: interaction with wp7 hd2 spl emulacrum and other parts+magldr. Will cotl' spl etc get wm6; should 'understand' wm6 os.nb?
Might lead to exploration of other partxx.bin from within wm6 or mtty. another thing is mtty. Mtty brings other ideas into play; if we know Cotulla and DFT layouts etc and truly understand magldr, partxx.bin, dwi.exe, and emulacrum spl, then we can go another way: that is all I am really saying here.
Especially considering how it is built and lack of tools/info on this ***particular*** wp7 build.
Click to expand...
Click to collapse
Ok.........
Anyone looked at rgu for serviceapp.exe or got anything on this? calls to DLL for Trivial FTP for FUU? Also: questions if any wouldnt mind:
anyway to tweak dwi.exe just like daf.exe and use switches like |ro| and other switches and set part layout size etc? originally thought could force magldr to convert-extract by putting other partxx.bins on part(0) user then do userdata dump to .img but layout! and prob it just dump in original .bin anyway? not quite sure how dwi places converts- containers, fs, etc?
Yeah, im being lazy, maybe too hopeful here on these (ffu/ruu) ones etc, but worth asking. These are what I will figure out/we need to. Also noted "wph" string in daf.exe for droid. interesting. so yes, bypass option seems real.
edit: going back to what I said above, replacing part04.bin COMPLETELY with equivalent size os.nb (rename back to part04.bin) and flashing with dwi.exe? there is a plethora of things that could be attempted this way. crc? size? errors? not sure, but there is that hd3/hd7 experimental leaked "hd2 wp7" rom that wouldn't flash to hd2 under normal spl. and a lot of other things here to do; I am just interested in this as it bypasses all normal known spl mechanisms completely! You can flash anything you want without checks etc. And then explore interaction with Cotulla' spl (wp7hd2LEO1000) and other partxx.bin etc. Thoughts?
As far as orthodox methodology goes, so, bepe_cotulla_dft made a complete new platform builder and bsp? thoughts on where to start without this?
Please note I am a windows (nt) kernel coder and getting my head around phone7, ie bsp/oal=hal (!) so please bear with me! Who is working on Transaction Safe exFAT? any progress towards cracking? what is Encryption used in TexFAT? Along with kernel/drivers (nt x86/x64) also have cryptography experience. Sorry for all the questions! umm, in summary:
I am also assuming other partxx.bin(s) of DFT release are SPL, OEM, OEM RO, etc.
***Anyone got up KITL and/or can debug this leo70 release? (please answer with instructions etc!).***
edit: with above factors being case, I will fully disassemble and reverse magldr, partxx.bin, cotulla wp7 hd2 spl, os.nb, dwi.exe later on . edit: am doing now. whilst reading architecture for windows 7 phone! Kitchen will be done, but ability to just flash and part layout initially required imho! I am going to take control of magldr, cotulla wp7 spl, dwi.exe first: doing this now .
Sorry to spread over few posts!
Ultimately thus, concluding, I think key here is to reverse engineer all (cotulla' wp7-hd2-spl emulacrum, magldr, os.nb, all other partxx.bins, dwi.exe) then create new open set of each these and new flasher: anyone explored this, disagree, agree?
This is what I am doing now .
Got IP address & can see what is being done.
i like your work
keep up what u doing and i hope to get it done so we can finally use wp7 unlocked and activated
thank you...
@Leo70
I'm a coocker (for windows mobile 6.X) so if you need some help i think i could help you. Just PM me if you need
Why don't you ask Cotulla? Reverse Engineering will be much more longer?
I think they are working on a new MGLDR so why do your own thing on your side?
Can you put a file in the installation process where we can put our Live ID Code?
If every one have the same market ID that will possibly be a problem in the future?
I'm not trying to teach you anything don't really now about dev stuff just wanted to share my thought and opinion.
looking forward to this kitchen....
ok, after 3 days of attempting to download RUU_Schubert_HTC_Europe_1.60.401.01_Radio_5.52.09.16_22.33a.50.10_Signed rom i had finally been successful so i thought i should try out swapping stuff to determine what each part**.bin represents.. started off with the basic os.nb swapping and tried flashing magldr to see the changes..
i hate to be the bearer of bad news but it seems partition size & info are hardcoded into DWI.exe so the file size change doesnt allow for a successful flashing..
so lets hope it will be more flexible when magldr 1.13 is released (which is going to be released "soon" as in no specific eta) otherwise this kitchen might just serve the purpose for building nb's/nbh's for other devices..
But im sure this issue is only present in magldr 1.12 dwi.exe as the wp7 rom wasnt released officially in xda, however only time will tell
Only time will tell, fingers crossed
this project sounds great. a already tweaked rom would be awesome and an pre activated rom even better.
keep up the work. maybe you should contact cotulla and ask him rather than reverse engineer everything. maybe he will help you and save you a lot of work.