Related
Is this (WM2k5_1.50g_XDA2_HIMALAYA.rar) newer then this
(WM2k5_XDA2_HIMALAYA_O2_FullRAM)
getting confuse.
I have a few question, please advise me.
1. extracted either files, and found that there is no (ms_) and (Radio_)
is this normal ?
2. i saw Radio 1.7.
Do i need to put Radio 1.7 together with NK.nbf and HimaUpgradeUt.
3. As for Protocol
Do i need to grab from the WM2003SE upgrade files?
I have read Wiki, but it did not mention about Radio 1.7 and Protocol
please guide me.
keithhiap said:
Is this (WM2k5_1.50g_XDA2_HIMALAYA.rar) newer then this
(WM2k5_XDA2_HIMALAYA_O2_FullRAM)
getting confuse.
I have a few question, please advise me.
1. extracted either files, and found that there is no (ms_) and (Radio_)
is this normal ?
2. i saw Radio 1.7.
Do i need to put Radio 1.7 together with NK.nbf and HimaUpgradeUt.
3. As for Protocol
Do i need to grab from the WM2003SE upgrade files?
I have read Wiki, but it did not mention about Radio 1.7 and Protocol
please guide me.
Click to expand...
Click to collapse
WM2k5_1.50g_XDA2_HIMALAYA.rar :shock:
to my knowledge g could be newer than f the one in the full ram version, so this potantially could be newer, as for the files ms & radio they have to be in the same folder as NK, regarding the protocol i have no idea what do you mean so please explain further
Basically, i am trying to claify by comparing WM2003SE files.
You see, when you extract WM2003SE, you will see 3 files (MS, NK and radio) right?
And in WM2005, you only see 1 (NK).
So, by my understanding, there is no Radio, and MS(in this case, this is protocol) in WM2005
Does it means that do i need to copy Radio 1.7 FTP: xda:xda and (MS) from WM2003SE into WM2005 folder?
pardon my english.
i see the screenshot for WM2005, and it has the radio 1.7 and protocol 1337.38
this really confusing me
Also reading the upgrading procedure. is just use patch 1, patching the NK files
then use ERedit and change the operator
this leads me that this file is only for OS.
So, as for radio and protocol (here i means , MS and radio), it is copy individual from different files and place it into the folder WM2005(here i mean going to upgrade)
thanks
by the way, this file WM2k5_1.50g_XDA2_HIMALAYA.rar is only 6.08MB, which is smaller then WM2k5_XDA2_HIMALAYA_O2_FullRAM (23MB)
Huh, I downloaded it and my rar file was 23695Kb, the extracted NK.nbf was 32769Kb.
I need my device at the moment so I dare not risk the upgrade at the moment. If anyone has performed the upgrade please post a line if it was successful.
cheers
hey guys,
there is nothing wrong with it...
i just uploaded it onto ftp. so if you have downloaded something smaller than usual size, you did the download before it was completely uploaded...
And yes, it is the newest version....
buzz
buzz_lightyear said:
hey guys,
there is nothing wrong with it...
i just uploaded it onto ftp. so if you have downloaded something smaller than usual size, you did the download before it was completely uploaded...
And yes, it is the newest version....
buzz
Click to expand...
Click to collapse
Buzz,
what are the enhancements done on it ?
Btw thanks you for the hard work once again...
buzz_lightyear said:
hey guys,
there is nothing wrong with it...
i just uploaded it onto ftp. so if you have downloaded something smaller than usual size, you did the download before it was completely uploaded...
And yes, it is the newest version....
buzz
Click to expand...
Click to collapse
Thnx Buzz, I just did the upgrade, no problems.. seems more stable... at least after running it for 5 minutes :wink:
Changes.log
Buzz,
Great and awesome work as usual
Just wondering if you can post a changes log or something so we can see any updates / changes you guru's have made
Just one question, in the final steps when we have to hardreset the pocket it's says format storage, it's internal storage or storage card?
eloco said:
Just one question, in the final steps when we have to hardreset the pocket it's says format storage, it's internal storage or storage card?
Click to expand...
Click to collapse
It's the internal storage eloco... Storage Cards ramain the same.
I'm getting reports from Newsmobile.it forum that this "g" version doesn't exposes the whole 128MB RAM amount........... :?:
Perhaps are there some additional steps to do?
I'm getting reports from Newsmobile.it forum that this "g" version doesn't exposes the whole 128MB RAM amount...
Click to expand...
Click to collapse
just flashed mine & memory is showing 62.00 for Storage and 56.34 for Program. I can live with 118 if this this image stops sucking my battery dry.
Can you list the differences/improvements?
Is the NAND Disk renaming to Sotrage the only change?
Can you list the differences/improvements?
Click to expand...
Click to collapse
I'm still waiting to see an improvement. Even with the slightly newer kernel I still see my battery dropping approx 1% per hour. Maybe that's OK, but with my radio, BT, and IR off I think it should do better than a 25% / day drop. If my radio was on, for 8-12 hours then 25% (maybe 40%) makes sense. I do notice that ActiveSync seems to load itself periodically (which I never saw using WM2K3SE), and I assume my serial port is being energized whenever AS loads. This could account for the power drop, but I'm still observing it. I haven't seen anything I could point to as an improvement.
I was hoping to see an improved video camera and working SMSs... :wink:
Oh well, I'm willing to wait whatever time necessary for better and better releases of BuzzMobile5.0
WoW another version from Buzz.... Buzz can u please whats the diff between the old and the new pls..
i've upgrade my xda with 1.50g, it works just great, with more stability on my device, but still with the minor bug (camera, and record button). i can see the program memory is bigger than the 1.50f, so i can open the 3mb excel file freely. now i can use the wisbar advance 2 without a bug, i think....
gadz, or anybody else with WM5, have you tried Wisbar 2.10.0.29 ? When I tried to run it, it would lock up until I renamed lrgwesex.dll. I'm also experience small graphic hic-ups, is anyone else?
http://www.lakeridgesoftware.com/forum/viewtopic.php?t=1977&start=15
OK, I've finalised an RUU Updater with inclusive tools to allow you to Bake your own ROMs from the ones already out there
this does NOT mean you can edit the OS files, simply mix'n'match
The RUU Updater also will run the SSPL for you meaning that you can use this RUU to flash *ANY* ROM to your PDA even if it is fresh out of the box (but please do take care when doing so)
There is no NBH included in this file, and you will need to place one in the directory you extract this to in order to run it.
Eventually I will release a GUI app to simplify the ROM baking process, but for now, feel free to experiment, and remember, you *CAN* delete components from the NBHGen sample file (say for example you didn't want to flash a new Radio), but please remember to ensure that all files are named correctly.
Download: (UPDATED VERSION, INCLUDES AUTOMATED GUI TOOL)
ftp://xda:[email protected]/Hermes/Tools_and_Programs/ModifiedRUUUpdater-V2.rar
Please note that the GUI tool is relatively primitive; please keep all files INSIDE the workshop folder, thanks
Credit:
- Credit to Pof et al. for NBHextract
- Credit to Bot for NBHGen
- Credit to Des for SSPL
- Credit to me for some rubbishy fiddling around
Olipro said:
OK, I've finalised an RUU Updater with inclusive tools to allow you to Bake your own ROMs from the ones already out there
this does NOT mean you can edit the OS files, simply mix'n'match
The RUU Updater also will run the SSPL for you meaning that you can use this RUU to flash *ANY* ROM to your PDA even if it is fresh out of the box (but please do take care when doing so)
There is no NBH included in this file, and you will need to place one in the directory you extract this to in order to run it.
Eventually I will release a GUI app to simplify the ROM baking process, but for now, feel free to experiment, and remember, you *CAN* delete components from the NBHGen sample file (say for example you didn't want to flash a new Radio), but please remember to ensure that all files are named correctly.
Download:
ftp://xda:[email protected]/Uploads/Hermes/ModifiedRUUUpdater.rar
Credit:
- Credit to Pof et al. for NBHextract
- Credit to Bot for NBHGen
- Credit to Des for SSPL
- Credit to me for some rubbishy fiddling around
Click to expand...
Click to collapse
I made NBH radio only upgrade posted here:
Here are Radio ROMs:
1.27 http://uploadingit.com/files/8194/NBH Radio Only 1.27.00.00.zip
1.33 http://uploadingit.com/files/8194/NBH Radio Only 1.33.31.00.zip
1.34 http://uploadingit.com/files/8194/NBH Radio Only 1.34.00.10.zip
Just a note: there's a GUI for the workshop now; remember that you don't have to create a NBH with EVERY .NB and you can select which ones to include (therefore, IPL and SPL can generally be discluded)
Thanks For The Files wpbear. Hopefully The First Of Many Cooked Software To Come From This Forum Now We Have Discovered The Secrets Of Our Hermes.
Cheers
will this still push SSPL onto the device while it is in bootloader mode? if so then this is the breakthrough everyone has been wanting for device recovery...
Olipro said:
Just a note: there's a GUI for the workshop now; remember that you don't have to create a NBH with EVERY .NB and you can select which ones to include (therefore, IPL and SPL can generally be discluded)
Click to expand...
Click to collapse
Nice GUI, not that DOS was real hard but the GUI is more convienent. Thanks
Still looking for a way to put my custom Ext_ROM into a nb file so I can truly cook my own ROM.
I Have A Problem When I Try And Start The GUI. I'm Assuming The GUI Is The File 'ROMBaker.exe' When Ever I Try To Run It, I Always Get An Error Saying 'The application failed to initialize proerly' Any Ideas?? Quick Question Was The GUI Written In C?
Cheers
do you have the .NET framework installed onto your machine??
mousey_ said:
I Have A Problem When I Try And Start The GUI. I'm Assuming The GUI Is The File 'ROMBaker.exe' When Ever I Try To Run It, I Always Get An Error Saying 'The application failed to initialize proerly' Any Ideas?? Quick Question Was The GUI Written In C?
Cheers
Click to expand...
Click to collapse
no, I wrote it with Visual Studio 2005, so you need .net framework 2.0
walshieau said:
will this still push SSPL onto the device while it is in bootloader mode? if so then this is the breakthrough everyone has been wanting for device recovery...
Click to expand...
Click to collapse
no, not even HTC could pull that off.
Olipro said:
no, not even HTC could pull that off.
Click to expand...
Click to collapse
hahaha thought so...
The GUI part NBHExtract is not working, it just sits there, gives no feedback or HD activity. I have all .Net installed 1, 2 and 3.
Generate NBH works to make your txt file. Then go to CMD prompt to run "nbhgen" [txt file].
I created New Cingular ROM with upgraded Radio and SPL 1.04.
Cingular WWE
OS/Ext_ROM (standard) 2.06.502.3
Radio 1.34.00.10
SPL 1.04
wpbear said:
The GUI part NBHExtract is not working, it just sits there, gives no feedback or HD activity. I have all .Net installed 1, 2 and 3.
Click to expand...
Click to collapse
thanks, I'll check this out and release a fixed one if it's not working
Yes, my mistake indeed, I wasn't cleaning that string properly,all sorted.
either redownload the RAR file or download the attached ROMBaker.exe and overwrite the old
Nice Work Olipro.
Would It Be Possible For You To Write A Quick Walkthrough On How To Use Your ROMBaker Tool?
Cheers
Thanks OLIPRO, great job man.
Olipro said:
Yes, my mistake indeed, I wasn't cleaning that string properly,all sorted.
either redownload the RAR file or download the attached ROMBaker.exe and overwrite the old
Click to expand...
Click to collapse
The new RomBaker still bad for me. The NBHextract opens a quick DOS box then immediately closes, no extraction.
yes, fixed everything now, and tested it properly, my mistake.
RUU on FTP is updated, or use the new attachment
Olipro said:
yes, fixed everything now, and tested it properly, my mistake.
RUU on FTP is updated, or use the new attachment
Click to expand...
Click to collapse
Works! Thanks.
Too good, just flashed 3.3 test OS, spl 1.04 and radio 1.27,piece of piss.
Great Job
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.
I recently have found that to have a rom fit for my needs and to work properly with my exchange server settings, etc. that I need to rebuild roms (easier than starting from scratch). I am not planning on re-distributing them, they are mainly for my use, and others that use a specific exchange server setup like I do.
Anyway onto my main question:
Using the different tools I have found through Google and xda-developers, I have started to extract the radio nb file so that I can build a new NBH with the radio and the rom. I have also toyed with the idea to do the SPL into the NBH so that I don't have to worry if it has been flashed or not. I also will be flashing the roms from my microsd card (which I have been doing with my modified rom already).
Thank you in advance!
Putting an OS and a radio in a single NBH is perfectly acceptable. However, I don't think you can include Hard-SPL in there because it is flashed through SSPL, and it should really be the only thing flashed in that manner.
Trancecoder said:
Putting an OS and a radio in a single NBH is perfectly acceptable. However, I don't think you can include Hard-SPL in there because it is flashed through SSPL, and it should really be the only thing flashed in that manner.
Click to expand...
Click to collapse
Got it, thanks for the quick reply too!
I noticed your signature, and saw that you have the rilphoneauto. I see an EXT and OEM type file, but I am only familiar with cooking in cabs and making minor entries. I wouldn't know where to begin to add in an OEM or EXT to the roms that I modify/re-cook.
They're basically directories with a slightly varied structure that you put in an appropriate kitchen directory and then select inside the kitchen UI. If you're using the new "visual" kitchen, you should use the EXT package; otherwise the OEM. There are tutorials all over the forums explaining how to use them. I'm probably not the best person to do it anyway since I've only been cooking for a little while
I've been struggling over the past few days trying to get the latest AT&T ROM working in a kitchen. I've tried three different workstations and two Virtual Machines assuming it was an environmental issue.
As a result, I decided to create a fresh new "old style" (PkgToolsBuildOS) kitchen on the assumption that something was wrong with my kitchens.
Noticed the following anomalies in the fresh new kitchen:
1) XIP.BIN / OS.NB.PAYLOAD
Noticed that when performing a Find Date/Rom Version on PAYLOAD or Find Date/ROM Version on XIP_OUT.BIN using XIPPORTEREX 1.2 rev32 , I get the following information:
Date: 06/May/2009
Rom Version: [K] InitDr
I've used the standard process that I always use which yields a working OS.NB.PAYLOAD and even validated it against Aruppenthal & Da_G's sk00ling.
Essentially: PP Unlock, NoCert Patch, PP = 6 MB ... same OEMXIP & MSIXP kernel for now just to try and get it to work.
2) Compiled ROM
If I change the ROM Version & update the Date (as per usual), the ROM compiles fine and boots. However, I am unable to connect to browse the Internet even though the 3G/H data connection appear indicating that a connection is established.
The ROM, OEM, SYS are all 20771 (5.511.502.2) for now just to try and get it to work using my Rogers SIM.
Has anyone else run into similar anomalies before? Cause I'd sure love to know what the heck I'm missing/doing wrong.
* EDIT *
Some of the "paranoid" measures I have done: Rootkit Scan, Full Anti-Virus Scan, Mem Test, Hard Drive Diag, CHKDSK, Restart, typical IT stuff ...
I'm not really sure what could be wrong, but if you need the dump set up for Visual, I had no problems dumping it and uploaded the untouched "Kitchen" to my FTP. Its labeled correctly as the build number 5.11.xxxx. I wish Icould help more, as you have helped me out a bunch.
EDIT: I did dump a ROM recently and got the same Version ID with xipporter as you have mentioned, but thought nothing of it. And I dont remember which it was, so sorry still not very helpful.
The ROM Version "garbage" is odd and IMHO should not be like that - your confirmation that you saw the same thing is very helpful ... at least I'm not losing my mind completely.
I'm trying to keep a PkgToolsBuildOS (5.3) and a Visual Kitchen (9.8) going for folks to use.
I had gone through all of the effort to port 21051 (SYS) and 20771 (OEM) in the hopes of posting it up before the end of the weekend ... then I started running into these unexplained issues and ended up scrubbing the lot.
I'm in the midst of recreating a new Visual Kitchen (9.8) and am discovering additional files in the OEM folder that weren't there before in older versions of the Visual Kitchen - not sure what it means yet; sure hope it doesn't mean having to recreate a kitchen everytime there's an update to the tools.
Cheers,
hilaireg said:
I've been struggling over the past few days trying to get the latest AT&T ROM working in a kitchen. I've tried three different workstations and two Virtual Machines assuming it was an environmental issue.
As a result, I decided to create a fresh new "old style" (PkgToolsBuildOS) kitchen on the assumption that something was wrong with my kitchens.
Noticed the following anomalies in the fresh new kitchen:
1) XIP.BIN / OS.NB.PAYLOAD
Noticed that when performing a Find Date/Rom Version on PAYLOAD or Find Date/ROM Version on XIP_OUT.BIN using XIPPORTEREX 1.2 rev32 , I get the following information:
Date: 06/May/2009
Rom Version: [K] InitDr
I've used the standard process that I always use which yields a working OS.NB.PAYLOAD and even validated it against Aruppenthal & Da_G's sk00ling.
Essentially: PP Unlock, NoCert Patch, PP = 6 MB ... same OEMXIP & MSIXP kernel for now just to try and get it to work.
2) Compiled ROM
If I change the ROM Version & update the Date (as per usual), the ROM compiles fine and boots. However, I am unable to connect to browse the Internet even though the 3G/H data connection appear indicating that a connection is established.
The ROM, OEM, SYS are all 20771 (5.511.502.2) for now just to try and get it to work using my Rogers SIM.
Has anyone else run into similar anomalies before? Cause I'd sure love to know what the heck I'm missing/doing wrong.
* EDIT *
Some of the "paranoid" measures I have done: Rootkit Scan, Full Anti-Virus Scan, Mem Test, Hard Drive Diag, CHKDSK, Restart, typical IT stuff ...
Click to expand...
Click to collapse
Several of the new builds are this way. Its because the date info has been moved. Until someone figures out which part needs hex edited we are stuck with stock dat Version changes fine.
Are you saying that we should *no longer* be changing the ROM Version and ROM Date?
In my case the Date "looked" ok but the ROM Version was bogus.
Which leads to these questions:
Does this also mean that PagePool Unlock, NoCert Patching, PagePool sizing are also in jeopardy of moving? (I know you or others won't have an answer for this one as it's in the hands of the OEM).
Does this mean that PkgToolsBuildOS kitchens and supporting tools are now at end-of-life?
Hate that when I forget to read the memo
UPDATE
Well, after an all-nighter ...
I can confirm that attempting to change the ROM Version and/or ROM Date via XIPPorterEX, PkgToolsBuildOS6.x-5.3, or Visual Kitchen 9.8 will indeed mess up the ROM - at least on the Raphael.
hilaireg said:
Well, after an all-nighter ...
I can confirm that attempting to change the ROM Version and/or ROM Date via XIPPorterEX, PkgToolsBuildOS6.x-5.3, or Visual Kitchen 9.8 will indeed mess up the ROM - at least on the Raphael.
Click to expand...
Click to collapse
So am I correct in assuming that when I change the PP in the 21806 version (as posted by Da_G) it is not really changing the PP. I did wonder why the amount of RAM didnt increase
B4PJS said:
So am I correct in assuming that when I change the PP in the 21806 version (as posted by Da_G) it is not really changing the PP. I did wonder why the amount of RAM didnt increase
Click to expand...
Click to collapse
The PagePool seems ok on my 6.1 builds at the moment but Da_G could best confirm that as he's been on this "circuit" way longer than I.
An observation I made, while I've been working on this, is that the PP size on the AT&T 5.11.502.2 seems to be set 1MB ... at least that's what XIPPorterEX 1.2 rev32 reports when I issue a change to the PagePool to 16MB on a non-reduced ULDR os.nb.payload.
Hmmm, Wonder why when I change my PP to 0 I still only have 197mb Total instead of about 213mb total? Might have to do a test and set it higher to see if my free space decreases
UPDATE: Direct From Da_Grand Pubba ...
Just had a quick chat with Da_G and he confirms that there's been a change in the XIP modules.
At first glance, he noticed that the NK.EXE module has three (3) new resource strings. So in short, if the ROM Version happens to display [K] InitDr (which is [K] InitDriverGlobals) DO NOT attempt to change the Date/ROM Version.
He also had a quick look for Certificate Patching, PagePool Unlock, and PagePool resizing - these appear to be untouched at the moment.
HTH,