Many users have asked me for some of the Rilphone.dll's of different radios. What I am attempting to do is to make one central location for all of the rilphone.dll's to be posted. Here is a couple that I already have on my machine. I will work at getting some others later on this evening.
If you are posting a rilphone.dll, please include the name of the device it comes from and the radio number it pertains to. Also, it would be really nice if users posting rilphone.dll's if they would just attach the zip file rather than linking to rapidshare, megaupload, 4shared or whatever. The files are small enough to just attach to your actual post.
If I have missed one that you require and you can't find it, please PM me and I will see what I can do.
Thanks for helping out in advance.
More Raph Rilphone.dll zip files
Thanks to Chainfire (Author of DriverWiz see post #15) I have created cabs of the different dll's I already have posted. These should work even if the nk.exe is not patched. Understand, that if it doesn't work, a HR might be in your future. Please test at your own risk.
Blackstone & Quartz Rilphone.dll Cabs
Thanks to Chainfire (Author of DriverWiz see post #15) I have created cabs of the different dll's I already have posted. These should work even if the nk.exe is not patched. Understand, that if it doesn't work, a HR might be in your future. Please test at your own risk.
Warning:
Please be warned that the X1_Rilphone_1_14_25_55.cab will freeze your device at the first boot screen. I am leaving it attached for others to play with and see if they can get it to work, but for now, it does not work with our devices.
Raphael Rilphone.dll Cabs
Thanks to Chainfire (Author of DriverWiz see post #15) I have created cabs of the different dll's I already have posted. These should work even if the nk.exe is not patched. Understand, that if it doesn't work, a HR might be in your future. Please test at your own risk.
- Requested Rilphone.dll's -
This will be for misc. requests. Just PM me and I will post the requested files. Thanks to everyone for the great responses. This forum just blows me away continuously with the great people we have here.
The attachments are just the dll's in zip format. The cab's will be with the other cab posts.
One more for the Blackstone
ok so i am not very familiar with this kind of file. when i unzip the folders you provide it shows the new folder as being empty taking up quite a bit of size.
how do i handle this file?
FatalCharade said:
ok so i am not very familiar with this kind of file. when i unzip the folders you provide it shows the new folder as being empty taking up quite a bit of size.
how do i handle this file?
Click to expand...
Click to collapse
The DLLs in the ZIP have hidden and system attributes, make windows explorer is set to show both.
Before the standard questions get asked here's links that explain :
Rilphone.dll ?
How to Install ?
k got it thanks.
Hey these were posted around the forum and in the radio thread. Credit goes to the persons who made them...sorry dont know who..actually.
About installing, stuff like this should always be installed with a signed CAB and DLL that injects its (your) own certificate into the privileged execution store. You don't need a patched nk.exe for that, and it works like a charm. I use this trick for all my 'system hacking' needs, and I know many other do too. I would advise against copying the file and renaming the registry as installation method - it's not proper. I'd be very surprised if this doesn't work for rilphone like Da_G said - I've never had this not work and I've replaced quite a few important system files on running systems.
Perhaps I should write a guide on this, as I see a whole lot of people fail at replacing system DLL's in various topics just because they don't do it right.
Chainfire said:
About installing, stuff like this should always be installed with a signed CAB and DLL that injects its (your) own certificate into the privileged execution store. You don't need a patched nk.exe for that, and it works like a charm. I use this trick for all my 'system hacking' needs, and I know many other do too. I would advise against copying the file and renaming the registry as installation method - it's not proper. I'd be very surprised if this doesn't work for rilphone like Da_G said - I've never had this not work and I've replaced quite a few important system files on running systems.
Perhaps I should write a guide on this, as I see a whole lot of people fail at replacing system DLL's in various topics just because they don't do it right.
Click to expand...
Click to collapse
Would you be so kind as to check my work? I have it signed and certificate stored in priveledged execution. I just want to make sure I've done it correctly. If it's wrong, then I've been doing it wrong for quite a while now.
Edit:
The cabs were not the correct way of doing things so I removed them.
Yeah you come ask me in chat and ignore me when I answer
Chainfire said:
Yeah you come ask me in chat and ignore me when I answer
Click to expand...
Click to collapse
I'm sorry. I never saw you reply. I just figured you were busy.
Right, here's how to do it properly:
http://forum.xda-developers.com/showthread.php?t=495145
Not sure if it will work for rilphone, but it's pretty likely
Chainfire said:
Right, here's how to do it properly:
http://forum.xda-developers.com/showthread.php?t=495145
Not sure if it will work for rilphone, but it's pretty likely
Click to expand...
Click to collapse
Worked perfect. Nicely done. And I rated it 5 stars.
P1Tater said:
Worked perfect. Nicely done. And I rated it 5 stars.
Click to expand...
Click to collapse
Your cab works perfect to.
I wanted to be sure so i also commited the trick of monx.
Afterwards i have implemented your cab and the rilphone is fully working.
In the beginning i was not able to fix this before i had the trick of monx. I was trying and trying. But now this combination wheter it was your cab or monx his certificate trick. I did it, so i'm happy now
hivesnl said:
Your cab works perfect to.
I wanted to be sure so i also commited the trick of monx.
Afterwards i have implemented your cab and the rilphone is fully working.
In the beginning i was not able to fix this before i had the trick of monx. I was trying and trying. But now this combination wheter it was your cab or monx his certificate trick. I did it, so i'm happy now
Click to expand...
Click to collapse
These cab's should work without the hex edit of the nbh. They should also work with a rom that does not have the nk.exe patched. Either way, I'm glad it worked for you.
thanks P1tater! cabs worked perfect my friend
Related
I seem to have successfully dumped my Cingular 8525 ROM, and placed it on the FTP area ftp://xdaupload:[email protected]/Hermes/Dumped_ROMs/ (directly as ftp://xdaupload:[email protected]/HTC_TyTn_Cingular8525_CWS_1_34_502_1_WWE.zip) but when I try to extract the imgfs I get lots of decomp errors and it seems that compressed files do NOT get uncompressed....
Is there something different in these newer ROMs or am I just being stupid or ????
TIA,
Richard
Moved the dump to safe heaven.
I haven't download your files to see if I can extract them, but if you not succeed with itsme rdmsflsh.pl you can also use mamaich rom editing tools, viewimgfs.exe with "part_02.raw". See if it makes any difference
pof said:
Moved the dump to safe heaven.
I haven't download your files to see if I can extract them, but if you not succeed with itsme rdmsflsh.pl you can also use mamaich rom editing tools, viewimgfs.exe with "part_02.raw". See if it makes any difference
Click to expand...
Click to collapse
It worked a little better, or at least differently.... I forgot to mention I tried that as well. Much harder to deal with the files being each in subdirectories The filesizes extracted still didn't match those reported on the device itself though, so I'm not convinced I'm getting a good extraction.
Results are on my work machine, I'll have to login there and see if I can post some specifics....
Richard
User error
rsolomon said:
Results are on my work machine, I'll have to login there and see if I can post some specifics....
Click to expand...
Click to collapse
DOH! User error.... Remote Desktop to my work machine slowed things down enough that I could see errors about not being able to load dlls.... seems the ActiveState Perl 5.8 install insists on installing to "site" vs "perl" but doesn't add "site" to the path, so Windoze couldn't load the necessary dlls.
I just copied them into my working directory for now and am re-running the extraction....looks much better already!
Richard
ok, can you add a warning to the wiki with this info ? thanks
pof said:
Moved the dump to safe heaven.
Click to expand...
Click to collapse
Should I add it to the wiki or will you do that?
Richard
pof said:
ok, can you add a warning to the wiki with this info ? thanks
Click to expand...
Click to collapse
Yep, I already noted one needs v5.8, I should really clean this up and find the right fix, but I'll note the path problem at least and maybe someone else will do it "right" later
Richard
do it yourself please, i have no time now... leaving to France in a few hours.
pof said:
do it yourself please, i have no time now... leaving to France in a few hours.
Click to expand...
Click to collapse
Both wikis updated, thanks for the help!
Richard
rsolomon said:
The filesizes extracted still didn't match those reported on the device itself though, so I'm not convinced I'm getting a good extraction.
Click to expand...
Click to collapse
Ok, pretty confused here. One example:
bthasplugin.dll
Exploring the device via ActiveSync shows a filesize of 17560 but the size shown on my PC of the extracted version is 18944. Spot checking a few other files show similar size disparities.... is this normal? Why?
Richard
Not sure, but probably the difference is because file size (byte count) is different than size on disk (amount of clusters the file takes).
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.
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
I'm on of those guys who hates the windows 6.5 Honeycomb menus. So after reading some points here I changed mine. Now you can to!
AwesomeStart is a modification to WM 6.5 that gives you a nice simple list that's fun and easy to use. Just install the cab and you're good to do.
Better yet, couple it with JSPA's Program Manager and my own Start Menu Sorter and you'll have the best menu in town.
Click here For JSPA's Program Manager
Click here for Start Menu Sorter
Note this is for WVGA (480x800) devices running Windows Mobile 6.5 and supports both Portrait and Landscape.
- Update - Sorry, forgot the cab file.. now it's attached.
Da Pitch
Hey.. you like my stuff? Please donate to support my independent film projects.
And please, watch my movies..
http://www.evanscitystories.com
(Rated Mature for Language and Gore)
BE SURE TO COMMENT AS I LOVE FEEDBACK!
This post...
... intentionally left blank!
Not Working...
I just tried your app on my TP2 CDMA with Mighty Mike 6.5 ROM and it does not appear to work unless there is something I'm missing.... but it seemed pretty strait forward...
Any ideas or comments?
Not working either
tried but does not work on my HD2
"installation unsuccessful"...strange!
Weird.. the only thing I can think of is for some reason the cab refuses to overwrite files in your windows directory. I'll attach just the source files. Just unzip them and copy the files in to the \Windows directory on your device.
Vga pleaaaaaaaaaaaaase!
zip file
So just copy this Unzipped file and put into -windows-?
Copied the contents of zip file and then did a soft reset but doesnt seem to work on the HD2
Doesn't work on HD2. Tried cab and tried zip to overwrite files. Neither work after soft reset. Plesse kindly fix as I SO want this.
Cant get it to work on my TP2 with HTC 6.5 rom either...?
Works great on my Rhodium, thanks!
Strange about the HD2. Can you see what StartMenu_GridScene files you have in your windows directory? Maybe they are by a different name.
JoeWilcox said:
Strange about the HD2. Can you see what StartMenu_GridScene files you have in your windows directory? Maybe they are by a different name.
Click to expand...
Click to collapse
nope, they are the same name, just verified. I can confirm it isnt working for my HD2 either
** edit
and can also confirm that the files in your cab are now in the windows folder. Backed up the old ones and the new ones have different modified dates
JoeWilcox said:
Strange about the HD2. Can you see what StartMenu_GridScene files you have in your windows directory? Maybe they are by a different name.
Click to expand...
Click to collapse
They are by the same name but there are also the following files which may or may not require modifying..
StartMenuCust_480x800.cpr
StartMenuCust_800x480.cpr
StartMenu_Global_800x480.cpr
StartMenu_Global_480x800.cpr
ok i figured it out guys, i attached a zip containing the 2 files that also have to be included. just copy these into your windows folder along with the cab in post 1. Please include them in a new cab (if you like of course).
mallman said:
ok i figured it out guys, i attached a zip containing the 2 files that also have to be included. just copy these into your windows folder along with the cab in post 1. Please include them in a new cab (if you like of course).
Click to expand...
Click to collapse
Thank you mallman...confirmed working. And thanks to the OP
worked after adding those extra files, thanks!
Also, curious if we can have the ability to get 2 columns in the landscape, since Its a waste of space to have only 2-3 on one view, so its also an even amount (Same amount seen in portrait as landscape)
So it seems that some roms use StartMenuCust_xxxx to get the grid layouts but not all of them. I've rebuild the cab and included the duplicates. Give this a try and see if it installs and fixes the problem on the HD2's.
Also, curious if we can have the ability to get 2 columns in the landscape, since Its a waste of space to have only 2-3 on one view, so its also an even amount (Same amount seen in portrait as landscape)
Today 08:52 PM
I've already been there and personally I didn't like it. You can edit the files yourself. They are pretty simple to work with. If you make them, feel free to PM me and I'll put them on the top of the page.
Vga pleaaaaaaaaaaaaase!
If there is enough demand I'll create them for a VGA device though I don't have one to test. I want to say someone else did already but when I searched I couldn't find it. I
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.