Related
Is there a site where all the known passwords for all the different ROMS are published? I have the passwords for 2.06, 1.72 and 1.66 but I'm trying to open the original 1.03.00 ROM files. ER2003Edit tries to guess with some defaults but none seem to work?
I tried searching, but didn't find anything for that ROM version.
Thanks
JamesManios said:
Is there a site where all the known passwords for all the different ROMS are published? I have the passwords for 2.06, 1.72 and 1.66 but I'm trying to open the original 1.03.00 ROM files. ER2003Edit tries to guess with some defaults but none seem to work?
I tried searching, but didn't find anything for that ROM version.
Thanks
Click to expand...
Click to collapse
There is a very good chance that the 1.03 ROM files are not encrypted at all. Try viewing one with a hex editor and if the content is readable (i.e. contains real words not just all gibberish) then they are not encrypted.
Passwords
Hey DCS, (btw: excellent work on the 2.06 ROM).
I think you're right. I've found words in the radio ROM, and the ExtRom... These files both end in .nb where the OS (which is encrypted ends in .nbf)
So I have a question then, (if you can lend a hand). I have the original ROM from HTC, (at least according to the iMate tech who sent it to me). It's the original 1.03.00 OS, Radio 1.05.12. When I run the downgrade it writes the OS and Ext but erases the radio and gets to 12% of the 1.05.12 radio and fails? Is it possible it's because this radio is not encrypted and the HimaUpgradeUt.exe thinks it can't read it? Shouldn't it have failed at the ExtRom? Using ER2003Edit it is not able to open any of the files so I don't know what the password UpgradeUt.exe is using to try to re-encrypt these two files?
Thanks,
What is the version of the upgrade program?
Passwords
The updater (HimaUpgradeUt.exe) is...
Version 0.0.7.0
Re: Passwords
JamesManios said:
The updater (HimaUpgradeUt.exe) is...
Version 0.0.7.0
Click to expand...
Click to collapse
That is ancient Maybe you could zip up all the nb* files plus the upgrade programs and send them to me. If so let me know and I'll send you a URL to use. Hopefully I can convert them to use a later upgrade program.
Passwords
Sure, I would appreicate the help. I think people might be interested in this update because it doesn't seem to care what you have installed it will overwrite anything and it's very clean; before vendors added any of their stuff to the Ext ROM.
Hi,
I really want to install the Alltel ROM on my Sprint Mogul. I've searched around and didn't come up with anything, so can someone more knowledgeable on the subject tell me if this is a good idea, or if it's begging to have my phone bricked:
I downloaded the Alltel ROM and extracted its NBH contents using nbhextract. The CID is set to ALLTE001.
I also downloaded the newest Sprint ROM and extracted its NBH contents. That one's CID is set to SPCS_001.
Can I use nbhgen to change the CID of the Alltel ROM to Sprint's?
*edit: Nevermind. Gave this a shot and just got an error from RUU.
Um, yeah you will get an error. And, why are you trying this in the first place?
I use Cricket for my service. I've gotten everything except incoming MMS to work, and the problem is with how Sprint's Data Provisioning is nested in the Mogul's Sprint ROM. There are IOTA settings in the registry, but I really have no idea about how to modify them since Cricket doesn't require any data provisioning.
On my 6700, ArcSoft would automatically dial the connection I had specified in the settings when an MMS arrived. Now, it attempts to connect to Power Vision, and I get an IOTA error about how the device failed to connect to Power and I should contact Sprint. I know that the Alltel ROM would not have these problems.
Another idea that I had was to completely replace my current registry with Alltel's (I have a complete dump), but I'm not too sure how to go about doing that, either. When I restore the file with PHM, the Sprint and Alltel settings just coexist with eachother.
If you have any ideas or suggestions here, they'd be appreciated.
my understanding of crickets data services was that they use simple ip and a proxy for http. have you changed the mogul to use simple ip? i think all you really need is a way of stopping an IOTA aka "vision profile update"
Exactly, but I'm not sure how to go about stopping that. My latest venture is to get someone with an Alltel PPC6800 to take a full SPB backup of the registry, so that their settings will overwrite all of Sprint's.
Do you know of a way to disable IOTA?
to0 said:
Exactly, but I'm not sure how to go about stopping that. My latest venture is to get someone with an Alltel PPC6800 to take a full SPB backup of the registry, so that their settings will overwrite all of Sprint's.
Do you know of a way to disable IOTA?
Click to expand...
Click to collapse
delete the guardian file in Windows startup - then delete the IOTA folder - in program files.. this is what I did to make the mogul work on Alltel before they launched the 6800. I also went through the registry and deleted a couple of IOTA registry keys.. I can't remember where they were though.. Finally, I deleted the error 67 notification in the registry and everything worked perfectly..
Now that the Hard SPL for the device is out you can install the alltel rom directly from the exe after the hard spl is installed.
Yeah I got this going a few days ago. MMS is working perfectly now!
I ran Olipro's unlocker and popped the Alltel ROM WITH the ExtROM and everything works WITHOUT any special consideration. You could say that it "worked straight out the box".
Now the qyestions are 1) now that I've unpacked the RUU_signed.nbh, how do I repack it, and 2) where is the extended rom in the unpacked nbh? I guess these are the big questions for getting Mogul kitchens together and cooking ROMs.
Yeah the Alltel ROM is running pretty well. Definitely an improvement over the stock sprint ROM. Not a huge difference, but it's definitely worth the upgrade until we get some ROM Kitchens/Heavily Modified/Improved ROMs.
don't u guys miss java support?
I can't run opera mini anymore once I switched to Alltel...
Install Esmertec Cloudyfa Java it's better than the builtin on Sprint. Saving space if anything
so how do i get the alltel rom on my sprint mogel? if i am with sprint
eakrish said:
so how do i get the alltel rom on my sprint mogel? if i am with sprint
Click to expand...
Click to collapse
go to ppc geeks and check out the 6800 forum.
instructions are at the top.
Is there a memory difference at all between the 2? If so, what is best to go with? What is the advantage to the Alltel one over the Sprint?...Sorry...kinda a n00b...but not really...lol
hate not having mms - flashin alltel now thanks guys!
RESOLVED:
if you are unable to use phone codes (like I was) then you are probably an idiot, just like I am. Go back to DCD's original post and make sure to install a Carrier ROM (linked to very clearly in his first post).
Many thanks to Santehnik for providing a workaround and to GC14 for providing the actual solution.
###################################################################
I just flashed to the new 3.1.6 and am unable to access the phone codes (e.g. ##775#).
I tried entering it into the dialer (as well as ##DIAG#, ##DEBUG#, etc...) numerous times. Resetting my device and trying again. No love.
I also tried running \windows\EPST.lnk and \windows\EPST.exe. What appears to happen is that the program appears to load for 1/2 second and then disappear (presumably it is crashing, though I dont know for sure).
I re-downloaded the ROM on a different machine and reflashed my Titan, but it made no difference.
I also tried installing the Phone Codes .cab which adds phone codes to your Programs Menu, but those links do the exact same thing as the EPST.lnk (something flashes for 1/2 second and then is gone).
I have the Sprint Carrier Cab (3.39.10) installed and i'm on PRI Version 2.03_003 and I can make phone calls.
Has anyone else had this problem? Any suggestions?
Here are what the codes link to:
##778 = ..\Windows\EPST.exe ##778
#33284 = ..\Windows\FieldTrial.exe
#3424 = ..\Windows\DMRouter.exe /DIAG
#38278 = ..\Windows\Fuart.exe Fuart
~~~~~~~~~
Note to self, add that info to the Wiki plus a link to an archive of WM links to execute those functions.
bob, what dialer do you have installed?
First of all use ##778CALL (instead #)
And put files from zip into windows folder.
For me this works
p.s can you send Phone Codes.cab to santehnik.ua""gmail.com
I can't find it
For all of those I need 2 # key presses for them to work. I'm using DCD 3.16 w/ radio 3.39 if it makes a difference.
Also what the heck is fast uart mode? (##38278)
Here are what the codes link to:
* ##778 = ..\Windows\EPST.exe ##778
* #33284 = ..\Windows\FieldTrial.exe
* #3424 = ..\Windows\DMRouter.exe /DIAG
* #38278 = ..\Windows\Fuart.exe Fuart
Click to expand...
Click to collapse
Key two things:
1. FieldTrial, DMRouter, and Fuart are ##33284, ##3424, and ##38278 respectfully.
2. You should point out that for Sprint, there's an extra # at the end instead of pressing Send. (ex. ##778#)
gc14 said:
bob, what dialer do you have installed?
Click to expand...
Click to collapse
I have the default dialer installed. I am using the "stock" DCD 3.1.6 ROM. I havent installed ANYTHING since i reflashed. I dont even have my SD card popped in. It's as clean as you could ask for.
I tried using ##775[CALL] and it does exactly what clicking on EPST.lnk does - it flashes for 1/2 second and then disappears.
I have the Sprint Carrier Cab (3.39.10) installed and i'm on PRI Version 2.03_003 and I can make phone calls.
Click to expand...
Click to collapse
Ok are you sure you installed the sprint carrier cab? 3.39.10 is the radio NOT the carrier cab.
Also on Sprint you have to add a # to the end of the codes. ##775# with NO send. ##775 send is for other carriers.
I hate to break it to you, but those files that "resolved" your problem are IN the sprint carrier cab.
gc14 said:
Ok are you sure you installed the sprint carrier cab? 3.39.10 is the radio NOT the carrier cab.
Also on Sprint you have to add a # to the end of the codes. ##775# with NO send. ##775 send is for other carriers.
I hate to break it to you, but those files that "resolved" your problem are IN the sprint carrier cab.
Click to expand...
Click to collapse
You are correct that I incorrectly identified the radio cab as the carrier cab. However, I did an install of the Sprint Carrier Cab (that's how I got the radio). It was the one from the wiki that says it includes radio 3.39.10. You can find it here: http://forum.ppcgeeks.com/showthread.php?t=26119.
Also, I have to press ##775[CALL] in order to get to the PRL screen (as was suggested). Hitting ##775# does nothing. I followed all the instructions. It used to work for me on my previous build (DCD 3.0.4 and Radio 3.35) as ##775# but not since the upgrade.
Either way, copying those 2 files (which did not get installed by the sprint carrier cab) and using ##775[CALL] seems to work just fine.
You can "hate to break it to me" till you're blue in the face that it shouldnt be that way, but that doesnt change the fact that it is. I have no incentive to lie.
You are correct that I incorrectly identified the radio cab as the carrier cab. However, I did an install of the Sprint Carrier Cab (that's how I got the radio). I believe that it was 3.54 (though I dont remember for sure). It was the one from the wiki that says it includes radio 3.39.10.
Also, I have to press ##775[CALL] in order to get to the PRL screen (as was suggested). Hitting ##775# does nothing. I followed all the instructions. It used to work for me on my previous build (DCD 3.0.4 and Radio 3.35) as ##775# but not since the upgrade.
Either way, copying those 2 files (which did not get installed by the sprint carrier cab) and using ##775[CALL] seems to work just fine.
You can "hate to break it to me" till you're blue in the face that it shouldnt be that way, but that doesnt change the fact that it is. I have no incentive to lie.
Click to expand...
Click to collapse
Ok, first of all, I only say this stuff because if I had a dime for every person who doesn't read dcd's first post in his kitchen thread, I'd be a millionaire.
You did NOT install the Sprint Carrier Cab. You installed the Sprint Update Rom to get the radio. Again, that is not the Sprint Carrier Cab that is required for 3.1.6.
The reason you have to use ##775 send and not ##775# like all other Sprint customers, is because you did not install your carrier cab. Without the cab, it defaults to ##775 send.
It worked on 3.0.4 because a carrier cab was not required, instead you picked your carrier in the kitchen.
Lastly, copying those files might have "fixed" your ability to get to EPST or DMRouter, but not the correct way. Also, there are other very important files other than those that you are missing.
Click on dcd's 3.1.6 kitchen thread and read the ENTIRE first post.
Thank you GC. I have installed the Carrier Cab and updated the original post.
bobjase said:
I also tried installing the Phone Codes .cab which adds phone codes to your Programs Menu, but those links do the exact same thing as the EPST.lnk (something flashes for 1/2 second and then is gone).
Click to expand...
Click to collapse
bobjase, can you send me that .cab also. I've been looking all over for it. [email protected] - Thanks!
I post this under the ROM dev for numerous reasons.
The Radio thread is scattered with confusing information about it.
You may wreck your phone by just copying it over the existing one.
There seems to be a requirement to be met by the ROM (patched NK.EXE if I recall right).
There seems to be a patch if NK is not patched by the chef.
Can one really explain what's behind that file and interaction with the Radio?
Admins, if you mind this post here either delete or move though I think it's ROM
related.
tyguy said:
I post this under the ROM dev for numerous reasons.
The Radio thread is scattered with confusing information about it.
You may wreck your phone by just copying it over the existing one.
There seems to be a requirement to be met by the ROM (patched NK.EXE if I recall right).
There seems to be a patch if NK is not patched by the chef.
Can one really explain what's behind that file and interaction with the Radio?
Admins, if you mind this post here either delete or move though I think it's ROM
related.
Click to expand...
Click to collapse
I can answer part of this.
The NK.exe must be patched to allow signed dll files to be added to the rom.
I have not heard of any way to get around the nk.exe patch. If there is Id like to hear it
It remains to be seen if the rilphone dll really makes much difference radio wise. However it does contain some carrier specific stuff in some cases. Da_G is more capable of explaining the technical details.
Thanks arupp I thought so too that there isn't a patch though one of the chefs had a comment on that
http://forum.xda-developers.com/showpost.php?p=3296537&postcount=794
I couldn't find it.
Thank you for starting this thread. I had searched everywhere for the Cmonex's autopatcher, but couldnt find it. Da_G also referenced it in the Radio thread here: http://forum.xda-developers.com/showpost.php?p=3229451&postcount=1012
so to patch or not to patch. That is the question.
Do i patch if i have a custom ROM?
Do i patch if i have the leaked version of the touch pro ROM official HTC (well almost) ?
Good thread thanks.
Found the thread Monx and Da_G referenced here: http://forum.xda-developers.com/showthread.php?t=384137
Post with patcher here: http://forum.xda-developers.com/showpost.php?p=2812111&postcount=23
Wtf??? i need to read the thread a few more times bc im still not sure what to do
Cmonex's autopatcher program is not really intended for the end-user, but more for the chef (it needs to be applied to xip.bin or os.nb.payload)
Her post says it might work directly on the .nbh before you flash it, but it's not guaranteed. I haven't tried it that way either - only directly on nk.exe inside the xip.
So, what you want to do is use the autopatcher directly on the .nbh - but again her post says it's not guaranteed to work.
Da_G thanks for chiming in!
So let me recap:
NK.EXE patch tool designed for chefs, not for Joe Doe users
No direct patch/fix for existing installation
Patch to be applied in ROM image NBH not Radio image NBH (---> hard reset)
Effects not really clear
From what I've read the rilphone.dll interacts with the Radio ROM and may be beneficial for reception and battery life but it's not proven that there will be a positive effect on the GPS for example (we all have lag ).
Furthermore, wrong ril... /Radio combo my make Radio unusable.
For GPS issues a NVRAM fix must be applied (early hardware boot-stage fix) which may not be even possible with the current ROM basis.
Conclusion:
Keep your hands off copying whatever rilphone.dll files are flying around in the Radio thread into your Windows dir and play it secure until the chefs figured it out BUT keep this post updated for general information.
Please tell me if I'm wrong.
tyguy said:
Da_G thanks for chiming in!
So let me recap:
NK.EXE patch tool designed for chefs, not for Joe Doe users
No direct patch/fix for existing installation
Patch to be applied in ROM image NBH not Radio image NBH (---> hard reset)
Effects not really clear
From what I've read the rilphone.dll interacts with the Radio ROM and may be beneficial for reception and battery life but it's not proven that there will be a positive effect on the GPS for example (we all have lag ).
Furthermore, wrong ril... /Radio combo my make Radio unusable.
For GPS issues a NVRAM fix must be applied (early hardware boot-stage fix) which may not be even possible with the current ROM basis.
Conclusion:
Keep your hands off copying whatever rilphone.dll files are flying around in the Radio thread into your Windows dir and play it secure until the chefs figured it out BUT keep this post updated for general information.
Please tell me if I'm wrong.
Click to expand...
Click to collapse
I can say the majoriity of custom roms have the nk.exe patched. If you dont know if your rom is patched ask your chef.
if you look at rilphone.dll in a PE viewer app, you'll see some references in the file to "AGPS". I think it's simply setting AGPS on or Off......or it might be more than that but I do see some references to AGPS in that dll (using the latest dll provided in the 5.05 release which is about 500kb in size)
I notice that my reception varies with different ROMs. I would say that I was getting the best reception with the 5.05 ROM and the 1.11.25.01 Radio. Then when I switched to some custom ROMs, things get a bit worse. The signal strength seems to vary more and I find the phone often switching between 3G and Edge or between Edge and GPRS/GSM. It keeps doing that even when I stay in the same place. I'll make a call with 5 bars of Edge and by the end of the call, be on GPRS when I didn't physically more. Or sometimes the phone will hang on to an HSDPA signal until I drop a call and never switch to Edge, which has 3 or 4 bars of signal strength once it finally does switch. I would imagine that all this switching to different signals is wasting battery too.
1) Could this be an issue with the custom ROMs rilphone.dll? I'm using EnergyROM 1.1a and 1.11.25.01 at the moment.
2) How can I know which radio version my ROMs rilphone.dll is designed to work with?
3) Does having that NK.exe patched allow me to just copy in a different version of the file with no adverse affects?
TheSopranos16 said:
I notice that my reception varies with different ROMs. I would say that I was getting the best reception with the 5.05 ROM and the 1.11.25.01 Radio. Then when I switched to some custom ROMs, things get a bit worse. The signal strength seems to vary more and I find the phone often switching between 3G and Edge or between Edge and GPRS/GSM. It keeps doing that even when I stay in the same place. I'll make a call with 5 bars of Edge and by the end of the call, be on GPRS when I didn't physically more. Or sometimes the phone will hang on to an HSDPA signal until I drop a call and never switch to Edge, which has 3 or 4 bars of signal strength once it finally does switch. I would imagine that all this switching to different signals is wasting battery too.
1) Could this be an issue with the custom ROMs rilphone.dll? I'm using EnergyROM 1.1a and 1.11.25.01 at the moment.
2) How can I know which radio version my ROMs rilphone.dll is designed to work with?
3) Does having that NK.exe patched allow me to just copy in a different version of the file with no adverse affects?
Click to expand...
Click to collapse
-----------------------------------------------------------------
Only NRGZ28 should be able to answer your ????
As he as mentioned in 1st page of thread "
This ROM is CE OS 5.2.20764 (build 20764.1.4.3) and the version is: 5.05.405.1 ,all from official Raphael ROM." using same build with which 1.11.25.01 radio is attached. Obviously it should have same DLL file if he has not altered it during cooking.......
Here's a bit more of a technical explanation for the whole thing:
rilphone.dll is the 'interpreter", or the "middle man" inbetween the Microsoft-desgined "Radio Interface Layer" or RIL - you can think of it as the Radio ROM speaks spanish, and Windows Mobile speaks english.. so when a program wants to do something involving the cellular radio, say, determining the signal strength to display the "bars", it issues a command to the RIL.. the RIL forwards this command to rilphone.dll, which interprets it into an AT Command. rilphone.dll then communicates through a standard serial port connection through SMD9: to communicate back and forth with the Radio ROM. Any responses are then translated again by rilphone.dll, and passed on to the RIL.
So, let's say a new command gets added to the radio. In this case we'll use a new command that was in fact added in 5.05, [email protected] - if the rilphone.dll is not updated, it is not aware of this new radio command, and will never issue it to the radio ROM. So you'd potentially be missing out on whatever that command does. Also, if a change is made to the required format of some other AT Command, the rilphone.dll will not be aware of this change and still be using the old format.
Carrier-specific rilphone.dll's also have features that generic ones do not (such as the 5.05 rilphone.dll in the htc-branded build most custom roms are using) - one such feature is CNAP support for Rogers - it seems support is built into all radio ROM's, but if rilphone.dll does not have specific support for CNAP, it never reads the caller name into the registry for display on the dialer. There are a number of similar carrier-specific features i've observed.
That should cover the function of rilphone.dll and the reason you'd want to keep it on-parity with the radio ROM... and in some cases why you'd want to use an older rilphone.dll (to maintain support for CNAP, etc)
Now on to the nk.exe patch -
nk.exe is the "boot process" for Windows Mobile.. it brings up hardware to initial values and displays the radio/protocol/build version info on the intial boot screen.. nk.exe controls such low-level things as the size of the page pool, certificate checking, etc.
This is where the nk.exe patch comes into play.. it replaces the code that checks certificates with a "No Operation" - so the system now trusts all code installed, regardless of if it has been signed by a trusted provider or not - this is a good thing, as you control all code being installed on the device, rather than the OEM, and one would presume at the point you want such checks removed, you know better than the OEM
Without the nk.exe patch, when you replace rilphone.dll, the system checks it against it's internal certificate store, finds that it's not signed with a trusted certificate, and refuses to load it. This is why replacing rilphone.dll on unpatched ROM's results in no radio function.
Once you have a patched nk.exe you can replace any trusted file in the system with an unsigned file and not have to worry about the checks - note you no longer need sdkcerts.cab either as this is intended to load onto your device's root certificate store, and then manually sign the files you're replacing with the sdk certificates, then it would be loaded up as a trusted file.. however this doesn't work on drivers that are loaded early in the boot process, as there are 2 "states" of the certificate store - one early boot state where the drivers are loaded, where it's using a pre-defined set of root certificates (specifically sysroots.p7b in XIP, which contains 17 certificates from trusted root providers) - the 2nd "state" of the certificate store is farther on in the boot process, after drivers and services are loaded - this is when it would load in the sdk certificates and allow you to load manually-signed drivers. But again this is too late in the boot process to allow sdkcerts.cab to work for Drivers and Services - which is why the nk.exe patch is needed.
Note that any files/modules cooked into ROM are automagically treated as trusted, regardless of nk.exe patching status or if the files are actually signed with a trusted authority - it's assumed by Windows Mobile if the file is cooked into ROM, it must be trusted.
Incidentally, I believe this is the reason HTC created the "BootLauncher" service - so that they could load up services signed with their own stuff after creation of the ROM (patches, hotfixes, etc). Basically BootLauncher loads up during the services stage, and waits for a pre-defined period of time before then loading it's own set of services (wait time and services to load are defined in the registry under HKEY_CURRENT_USER\Software\HTC\BootLauncher)
the autopatcher searches for a string to replace, so it might work on the .nbh.. the feeling i get from cmonex's post is that she didn't design or test it against that scenario, but it might work
Hope that sheds some light on the situation, and isn't too complicated!
Hi DA_g
Thank you Da_g for such a beneficial explanation....
I hope its going more complicated now..... as you have explained
"Carrier-specific rilphone.dll's also have features that generic ones do not (such as the 5.05 rilphone.dll in the htc-branded build most custom roms are using) - one such feature is CNAP support for Rogers - it seems support is built into all radio ROM's, but if rilphone.dll does not have specific support for CNAP, it never reads the caller name into the registry for display on the dialer. There are a number of similar carrier-specific features i've observed."
all radios have Carrier-specific rilphone.dll's so obviously all its not only with 1.11.25.01 (Raphael radio) all other radio's i.e, for example .16,.19,.28,.32,.20 if so obviously the results would be not stable for all the users with different ROM's and Radio's.......... Now the big ? rilphone.dll should be programed for different carriers to the specific radio
The way it seems to work from my observations is this:
Carrier X issues a "ROM Request" to HTC, specifying what support and configuration they require (such as CNAP support for rogers)
HTC then assembles the ROM to their specifications, using the latest drivers, etc, available at the time.
All radio rom's seem to include support for all carrier-specific options, they just need a rilphone.dll that is aware of the particular option to enable it.
So for us to get a newer rilphone.dll with rogers support (say, 5.05), rogers would need to issue a "ROM Request" to HTC, and they would need to fill it.. then we would have the rogers 5.05 rilphone.dll.
Using an older rilphone.dll has unknown effects (as it will not be aware of newer features in new radio version, etc) but so far has not shown to cause specific issues.
Hi DA_g
I need your help regarding this...how to edit rilphone.dll i am working as switch engineer for Ericsson india for GSM ...hope fully i would be able to understand some of the specifications present in this file.
Editing a .dll is beyond the scope of my ability to explain in a forum post, you need to do some research into reverse engineering and ARM disassembly..
Particularly, if this screenshot scares you: http://www.hex-rays.com/idapro/pix/idalarge.gif
You probably don't want to even get into it
Da_G said:
Editing a .dll is beyond the scope of my ability to explain in a forum post, you need to do some research into reverse engineering and ARM disassembly..
Particularly, if this screenshot scares you: http://www.hex-rays.com/idapro/pix/idalarge.gif
You probably don't want to even get into it
Click to expand...
Click to collapse
Ha ha ha really it is scary...............
But in my opinion individual Radio should be mapped to rilphone.dll with carrier specification with out this non of the radio would give best result .....
Depends on one using carriers with different frequencies for example.... i got tp with radio ver .28 (raphael) which is made for IDEA operator which uses 1800mhz freq, where power of the cell site & TP might be programmed vious according in rilphone.dll.....
i did SIM unlock.....Now i am using TP on Airtel operator which work on dual band 900 & 1800 so it is obvious that RADIO would not give me best results.
Results are vigorous ....dropped calls, voice break, poor coverage, poor battery performance,e.t.c................
So all ROM with associated with RADIO would work better on TP who uses specified Carrier...
Is there a way to get or create an universal rilphone.dll ?
Only someone with access to rilphone.dll source code could create a universal rilphone.dll.
Quite doubtful that HTC would be interested in doing this
aruppenthal said:
I can answer part of this.
The NK.exe must be patched to allow signed dll files to be added to the rom.
I have not heard of any way to get around the nk.exe patch. If there is Id like to hear it
Click to expand...
Click to collapse
I think you mean unsigned.
there is a way around... you import your own certificate into the device's trusted certs store and then sign the system DLL with your cert and copy it over... WM accepts this no problem and this is exactly how I used to do things.
Can someone please upload Alltel PRI 1.28. The reason I need it is that it will get rid of my roaming triangle (have a sprint TP converted to Alltel). I found one over at ppcgeeks, but for some reason don't have permission to download it (even though I'm already registered there). And thanks in advance.
mickeyx323 said:
Can someone please upload Alltel PRI 1.28. The reason I need it is that it will get rid of my roaming triangle (have a sprint TP converted to Alltel). I found one over at ppcgeeks, but for some reason don't have permission to download it (even though I'm already registered there). And thanks in advance.
Click to expand...
Click to collapse
Here: http://forum.ppcgeeks.com/showthread.php?p=888469 Follow the instructions by ksg CLOSELY.
Yeah I saw that, but for some reason I can not download the file. It says that I don't "have permission to access this page." So, I was hoping that someont could upload the file here at xda. But. thank you for you help anyway.
mickeyx323 said:
Yeah I saw that, but for some reason I can not download the file. It says that I don't "have permission to access this page." So, I was hoping that someont could upload the file here at xda. But. thank you for you help anyway.
Click to expand...
Click to collapse
Here you go.. again, follow the instructions CLOSELY from: http://forum.ppcgeeks.com/showthread.php?p=888469
"Instructions to install:
1. Download PPST_080714_VictorC_Alltel_1.28_delta.sa.zip and unzip.
2. Connect your phone with ActiveSync and transfer PPST_080714_VictorC_Alltel_1.28_delta.sa.cab to your phone.
3. Run PPST_080714_VictorC_Alltel_1.28_delta.sa.cab from your phone
4. Using File Explorer (or total commander, or whatever you have...) go to \windows and launch PPST.exe
5. Answer yes at the prompts. Your phone will now reboot.
6. Go to start -> Settings -> Device Information and check to make sure your PRI version is now 1.28_011
7. Dial *228 and then select 1 to program your phone OTA. This should download the latest PRL for you and get your phone back out roaming, etc."
This will upgrade/migrate the PRI on any CDMA Touch Pro or Diamond to the Alltel PRI 1.28. DO NOT RUN THIS IF YOU DON'T WANT TO BE ON AN ALLTEL PRI. Good luck!
Hey thanks for all your help. I really appreciate it.