Related
i think most of you x01ht users in japan are aware that softbank issued a new rom update that has the new open.softbank.ne.jp password hard-coded as part of the rom image and so there's no way to extract it via extended rom or otherwise (it's not in the preconfig cabs/xmls either). they've also announced that after april 1, the old password which most of in japan are currently using will no longer work so we either upgrade to the new softbank rom or we can't access the open network.
anyway, i've been fiddling with this all night and i think i have a solution that i've tested on a couple of different roms but i'm hoping you guys can give it a try as well so that we can call this a solution to the problem. basically, i made the assumption that the password was somewhere hidden and encrypted in the registry though i had no idea where so basically all i did was do a registry dump with a clean install of the new sb rom, went into connections and deleted the softbank connection, then did another registry dump. finally, i did a compare of the before and after using windiff, figured out what changed and i ended up with the attached two reg files. one adds "SoftBank" as one of the connections (hklm.reg) and the other is the encrypted password (hkcu.reg). you need to import these using the registry plug-in that comes with resco explorer (just dl the trial) as that's what i used and it seemed to work. also, after you do the imports, MAKE SURE you power off (not reset) and then power back on. sometimes the registry settings don't stick if you simply reboot.
to really verify this works, you should first go in and delete your existing SoftBank connection in settings->connections tab->connections->manage existing connections (under internet). if you're not confident then go ahead do a backup beforehand or you can just run the sb extended rom again if you can't get it to work. i've tried this with the sb rom as well as an i-mate rom and it's working perfectly...i'll test it with a couple other tomorrow as well. if this works for you guys, i'll go ahead and make it into a cab file.
update: okay, i've gone ahead and made it into a cab so you don't have to muck around with importing reg files. so just download the cab if you want to run a simple cab install. the zip file contains the reg files if you want to manually import yourself. i've tested both and they work fine. again, i must emphasize that you power off after installing it and not just soft reset. try it out and let me know.
FOR THOSE OF YOU DOING CLEAN INSTALLS:
i didn't realize this but when you do a clean install, you still have to install a couple of the sb extended roms before you run my cab. specifically, you need to run PP_ConnVKK_1.33.761.1.CAB and Provisioning.exe to set up the device to even be able to accept the new password/settings. run PP_ConnVKK_1.33.761.1.CAB first and then Provisioning.exe...now once you run provisioning.exe, you'll find that it automatically creates the old SoftBank connection for you under internet->manage existing connections with the OLD password. go ahead and delete this connection, reboot (optional) and then run my cab (new sb settings.cab). power down and up again and it should work.
just to be sure i did a file compare of the [HKEY_CURRENT_USER\Comm\RasBook\SoftBank] "Entry" and "DevCfg" keys/entries with the old SoftBank setting active and with the new SoftBank settings active and the file compare showed that the contents were completely different. i was worried that maybe somehow the system was just somehow reviving the old password and not actually using the new one but this does not appear to be the case.
UPDATE:
after some more experimenting, it seems that the cab just restores the sb connection with whatever username/pass that you had installed previously. if you delete the the new opensoftbank username connection and then run the cab, it restores the opensoftbank username/password. if you delete the old "open" username connection, it restores that. very strange since the file compare shows that this registry dump (taken from new rom with new settings) is significantly different than a dump taken from a rom with the old settings yet it is somehow restoring the old settings. thanks for looking into this but for now, i think we have to say that this isn't working. so it seems that password is not simply stored in the registry. it must be in some hidden file that this registry dump somehow activates. in any case, i'll keep working over the coming weeks. sorry for getting everyone's hopes up.
Wow, I think that is great news for every Softbank customer!
Thanks it worked for me. I guess I will find out in April if it will work. I will cross my fingers.
Great job!!
You are the man! Great!!
thanks for checking! are you saying you're unsure if the file actually contains the NEW password and not the old one? well, it's definitely the new password as i created these files using only the new rom, a reg editor and a file compare tool so the old password never entered the picture.
you can actually run this exercise yourself and just repeat the steps i did if you want to be sure as the methodology is pretty simple. all i did was find where the encryped passwd was stored in registry and just imported it over to a different rom as is, encryption in tact. i've made no attempt to hack the actual passwd--we still have no idea what it is but as long as we can use the new settings, finding out what the passwd actually is unnecessary.
jokinawa said:
Thanks it worked for me. I guess I will find out in April if it will work. I will cross my fingers.
Click to expand...
Click to collapse
i haven't tried this yet, but if it works for you using the new ap opensoftbank now, i believe you don't have to wait until april to see if it'll work. those who've already upgraded theirs to the new rom should be using that new ap already.
i must try this myself later today.
trialdei, thanks for the great work.
that is indeed a great news, I was also wondering how to find this in the registery but was not sure that the different key I found were the correct ones. I will try on my other Hermes tonight and we shall see ! But the very promissing point here is that potentially I can even use these files for my universal and the mteor... which means... if you don't like the crap of the SB roms... just buy a WM5 device everywhere U want and put these regkeys !!!
Good job Man !!!
Yes this is great news, I think we might still need the password to use the phone as a modem connected to a notebook.
I think that is exactly what softbank does not want us users using the connection for since we would use the internet more.
okinz said:
Yes this is great news, I think we might still need the password to use the phone as a modem connected to a notebook.
I think that is exactly what softbank does not want us users using the connection for since we would use the internet more.
Click to expand...
Click to collapse
actually, i don't think you need to enter the password on the pc side at all to use the phone as a modem. check this post:
http://forum.xda-developers.com/sho...etooth+set+TyTN+to+be+discoverable#post987712
how about us with new sb rom... i don't see any wireless modem application on my phone... do you have a cab file for the wireless modem app alone?. i can't find it from ftp...
guys,
softbank is blocking the modem usage with a pc and it seems that's controlled at their open ap. i don't believe that's anything to do with the password nor the applications you use. you can fire up dun on your pc with x01ht connected via usb or bt, but the connection will fail.
harryk1372 said:
guys,
softbank is blocking the modem usage with a pc and it seems that's controlled at their open ap. i don't believe that's anything to do with the password nor the applications you use. you can fire up dun on your pc with x01ht connected via usb or bt, but the connection will fail.
Click to expand...
Click to collapse
i think you're probably right but then i wonder what's the point of establishing the new password in the first place if the modem usage isn't an issue for them either way? all of the x01ht's making their way to hk and abroad aren't going to be used on the sb network anyway. the new read-only radio rom takes care of simlocking already so the new passwd solves what? they just don't like the idea of people running around with foreign language roms accessing their network?
trialdei said:
so the new passwd solves what? they just don't like the idea of people running around with foreign language roms accessing their network?
Click to expand...
Click to collapse
i think they don't want people without the flat rate data tariff contract to use the open ap to cap the monthly pay. there are quite a few people in japan who just had the vodafone contract and running universal or hermes bought from elsewhere.
now that i have your registry solution for the new password, i cannot resist testing it on my universal. if it works, i don't have to retire my universal after april 1. thanks again.
trialdei said:
basically, i made the assumption that the password was somewhere hidden and encrypted in the registry though i had no idea where so basically all i did was do a registry dump with a clean install of the new sb rom, went into connections and deleted the softbank connection, then did another registry dump. finally, i did a compare of the before and after using windiff, figured out what changed and i ended up with the attached two reg files.
Click to expand...
Click to collapse
great job, trialdei. i have not tried this yet, but i will not have to give up a2dp if this works with the docomo rom!! many thanks!
i'm a newbie on this topic softbank open access.
so what is the main purpose of having this option available for the user.
is it allow the user to have the internet access over the softbank network.
and also if possible, please guide where i can find addititional softbank open access setup instruction, besides the information is already provided by trialdie's original post on this string.
please advice.
found the existing thread on softbank open access (unlock softbank x01ht thread). got the answer from there.
great!
this is great! i was having problems with the new sb rom and asukal's mui... i can't seem to get any network signal or even passthrough connections with that combination..
i'll try this one with the new htc rom from south africa, it may work for me.
great work dude!
no connection appears even after importing the reg with docomo rom... i will try it again when i have more time.
qtotter said:
no connection appears even after importing the reg with docomo rom... i will try it again when i have more time.
Click to expand...
Click to collapse
hi qtotter,
you need to make sure your registry settings are sticking...did you power off/on. the below new registry keys/entries should show up if you did it right:
[HKEY_CURRENT_USER\Comm\RasBook\SoftBank]
"Entry"
"DevCfg"
[HKEY_LOCAL_MACHINE\Comm\ConnMgr\Providers\{7C4B7A38-5FF7-4bc1-80F6-5DA7870BB1AA}\Connections\SoftBank]
"ConnectionGUID"
"SecureLevel"
"Secure"
"AlwaysOn"
"RequirePw"
"Enabled"
"EntryType"
"DestId"
if you don't see these new keys/entries then your registry changes aren't sticking.
trialdei said:
i think most of you x01ht users in japan are aware that softbank issued a new rom update that has the new open.softbank.ne.jp password hard-coded as part of the rom image and so there's no way to extract it via extended rom or otherwise (it's not in the preconfig cabs/xmls either). they've also announced that after april 1, the old password which most of in japan are currently using will no longer work so we either upgrade to the new softbank rom or we can't access the open network.
anyway, i've been fiddling with this all night and i think i have a solution that i've tested on a couple of different roms but i'm hoping you guys can give it a try as well so that we can call this a solution to the problem. basically, i made the assumption that the password was somewhere hidden and encrypted in the registry though i had no idea where so basically all i did was do a registry dump with a clean install of the new sb rom, went into connections and deleted the softbank connection, then did another registry dump. finally, i did a compare of the before and after using windiff, figured out what changed and i ended up with the attached two reg files. one adds "SoftBank" as one of the connections (hklm.reg) and the other is the encrypted password (hkcu.reg). you need to import these using the registry plug-in that comes with resco explorer (just dl the trial) as that's what i used and it seemed to work. also, after you do the imports, MAKE SURE you power off (not reset) and then power back on. sometimes the registry settings don't stick if you simply reboot.
to really verify this works, you should first go in and delete your existing SoftBank connection in settings->connections tab->connections->manage existing connections (under internet). if you're not confident then go ahead do a backup beforehand or you can just run the sb extended rom again if you can't get it to work. i've tried this with the sb rom as well as an i-mate rom and it's working perfectly...i'll test it with a couple other tomorrow as well. if this works for you guys, i'll go ahead and make it into a cab file.
update: okay, i've gone ahead and made it into a cab so you don't have to muck around with importing reg files. so just download the cab if you want to run a simple cab install. the zip file contains the reg files if you want to manually import yourself. i've tested both and they work fine. again, i must emphasize that you power off after installing it and not just soft reset. try it out and let me know.
Click to expand...
Click to collapse
its great but it did not work in my o2 xda exec.
thanks
Well, there you have it... that's the question, and the answer is obvious.
However, the caveat is not...
Does AEButton save your changes to the registry, or to a DLL?
Can someone tell me how I would go about cooking my personalizations into my ROM?
yes, you need to get the OEM package for it though. I have a lot of packages, but no aebutton.
you can one of two things....
1. learn how to create your own packages. there are a few tutorals here on xda.
2. send me the app and seriall number for activation and I will put one together for ya.
email is codyppc at gmail dot com
Cody,
thanks for answering, but i think you misunderstood...
I need some help figuring out how to make an OEM that will also set up all of my current button associations. I'm not sure if there's a DLL I need to pull off my phone and overwrite in the cab, or if there are registry entries I need to add to an RGU... I'm hoping someone has that info.
Any help?
badutahboy said:
Cody,
thanks for answering, but i think you misunderstood...
I need some help figuring out how to make an OEM that will also set up all of my current button associations. I'm not sure if there's a DLL I need to pull off my phone and overwrite in the cab, or if there are registry entries I need to add to an RGU... I'm hoping someone has that info.
Any help?
Click to expand...
Click to collapse
The easy way to find your answer is to use a registry compare program... Export your current registry, then change all the button assignments you want changed and then export the registry again. have the program compare the 2..... here's the registry program that I use to compare with... works great.... You should see the differences real easy if they are saved in the registry.....
azclown said:
The easy way to find your answer is to use a registry compare program... Export your current registry, then change all the button assignments you want changed and then export the registry again. have the program compare the 2..... here's the registry program that I use to compare with... works great.... You should see the differences real easy if they are saved in the registry.....
Click to expand...
Click to collapse
Thanks. I'll give your program a try.. I've been using windiff, and haven't been able to decipher the gobbledy-gook to figure out which registry entries are changed.
Here is a working AEButtons Plus OEM.
once you try user customization, you will love the flexibility in it. If a new program comes out, you can just uninstall your current version. Or, when you reflash you can just edit your SDconfig.txt
When you cook programs into the rom, you are stuck with that version
1999TL said:
once you try user customization, you will love the flexibility in it. If a new program comes out, you can just uninstall your current version. Or, when you reflash you can just edit your SDconfig.txt
When you cook programs into the rom, you are stuck with that version
Click to expand...
Click to collapse
Can you tell me how to set up AE button with user customization?
LOL. I forgot about that. yOu have to use the hide and unhide function in UC. It is posted in the UC thread. I'm laughing b/c i just remembered AE button plus gave me the hardest time at first, until I found out about the hide and unhide.
When you install AE button plus, it pulls you up to the program menu screen. That will just freeze User customization. So you have to be in unlock mode. I actually just install AE button plus and .net 3.5 upon start of UC, then I lock the phone and let it do the rest.
AE Button Plus stores its config in AEBPlus.cfg. This stores the button config as well as your registration data. That file needs to be in the same directory the rest of your AE Button plus files are.
EDIT: I have attached the OEM I use for mine. It has my AEBPlus.cfg in it which you will want to overwrite with yours. Otherwise, you will have my config as well as my serial # which is only good for my device.
Thanks guys! you're all awesome.. thanks for the help..
I'm going to try to cook AE into my next rom.. with that success, I think I'm only 1-2 steps away from having PERFECTION on my phone... haha
hey all!!
i'm from Venezuela and i recently purchased a HTC PPC6800 (cdma) and my carrier here didn't activate the GPS...
I'm not new to windows mobile but i'm totally new to ROM upgrading...
the only thing im affraid of is not being able to make calls after the upgrade... since i'm from Venezuela i can't use Sprint configuration...
so here's my question:
WHAT DO I HAVE TO BAKCUP FROM THE FILE "EPST" SO I CAN SET IT UP AFTER THE UPGRADE???
i'll be very much appreciated if any of the Senior members could help me here...
thanxs!!!
Nelson
HTC PPC6800
Caracas - Venezuela
Movilnet
Nelson, there is a few month old utility that can extract an HTC ROM from the device directly to the SDcard. If you have the ROM (*.nbh) of your phone from your carrier then you could use a utility such as DogGuys Kitchen maker to decompile the ROM. What you usually only need is contained in the ..OEM\OPERATORS directory.
If you look at how existing kitchens (and a FAQ on kitchens) are set-up, you'll see that each carrier tends to have its own operators OEM that the end-users selects when building their ROM. Following those templates you can create your own with the files specific to your carrier, and add that to an existing kitchen. Once done, then you can then build your own ROM. Though, with that done, of course the language files for your new OS ROM will be english rather than spanish.
The other possible option is to provide your carrier's OS ROM to the forum here and one of us may have the chance to decompile the necessary files and provide a set-up for you.
...sorry, I'm travelling right now and don't have the chance to go into greater detail or updated links.
whoa! I think u went way over his (and my) head with that one...
I don't think he's looking to cook his own rom, he just wants to install one....and wants to know what info he needs to document before so he can reinstall it properly afterwards..
wow thanks Keystone...
although Dillsnik is right... i read the FAQ on kitchens an it doesn´t sound complicated... but i´m not sure if i´m capable of doing this...
however i will be reading more about this kitchens and cooking my own rom because it sounds very interesting that i can put only the programs i want (wich by the way it´s exactly what i´m looking for), so i´ll be witing here soon asking more questions...
by the way, the main propuse of this thread is still open... and the quistion is in the first post:
WHAT DO I HAVE TO BAKCUP FROM THE FILE "EPST" SO I CAN SET IT UP AFTER THE UPGRADE???
thanks for the quick response!!!!
guys, installing the official Sprint rom before your rom of choice allows your carrier settings to be maintained, so there is no need to back up any of that information. at WORST, you'll have to get your a-key reset, which is a quick call to verizon(or your carrier?). i've only had to do this once, and i've flashed my phone probably 25 times.
install olipro 2.4
run Official Sprint RUU
at 'Tap Here to Set Up Your Device' install your rom of choice
run carrier cab (if its not in the kitchen)
if you try to make a call and receive a 'your phone cannot be authenticated' message, call tech support and dont let them tell you anything, just say 'i had to do a hard reset and now my phone cant authenticate i need a new a-key please.' theyll tell you that its not necessary and will try to do it automatically, then if they cant theyll give you a new a-key and tell you how to apply it.
EDIT: there is no way to view your a-key, which is why you are unable to back it up and why backing up EPST settings is pointless for you.
nelsongruebr said:
wow thanks Keystone...
although Dillsnik is right... i read the FAQ on kitchens an it doesn´t sound complicated... but i´m not sure if i´m capable of doing this...
Click to expand...
Click to collapse
Well, I think Keystone is trying to give you a safeguard. You likely have a ROM that nobody else has a copy of here, and I'd suggest you dump a backup copy of it before you do anything to your device, just in case.
WHAT DO I HAVE TO BAKCUP FROM THE FILE "EPST" SO I CAN SET IT UP AFTER THE UPGRADE???
Click to expand...
Click to collapse
We cant give a definite answer to that because we do not know how your carrier operates.
In theory, the actual Sprint update should backup your programming and restore it for you. I do understand you wanting to have a backup plan, but in that case, I would suggest you record everything.
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.
Hi all,
I was trying to modify the ActionMenu that pops up when you slide the querty out. This is on a HTC S740, but I suppose it would be the same for all HTC devices with a slide out keyboard. My intention was to edit it in a way that option nr. 3 (messenger) brings up a different messenger than WLMessenger, as I never use this one.
My findings so far are that the information to the links are stored in a dll called ActionMenu in the windows folder. I was able to open it with notepad, however editing the path for the messenger somehow broke the whole dll so ActionMenu won't pop up at all anymore when sliding the keyboard open. I also tried editing it with XN Resource Editor, but there nothing is displayed. So for now I am at my wits end.
Maybe someone else could help out here? Would truly be appreciated.
Regards,
.-ombre-.
Dll is a compiled library and therefore a binary file... If you would like to edit it this brute way you should use hex editor and only REPLACE links. That means, new link must have the same lenght as the old one and none of bytes should be moved. Then obviously, final file must have the same size as the old one.
Anyway, then it mustn't work either.
yeah, thats something I tried in the meantime and no, that doesnt work either..
Oh well..