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
Hi folks,
Although I am generally not timid about modding certain products (such as my computers and TiVo), I do like to first take my time before diving in until I'm sure I've read most of the relevant threads and have gathered up the complete suite of software tools in one place. The resources on this site and the work of folks such as DCD and nueChem are amazing and outstanding and I want to say thanks for that.
As of yesterday, I felt read to take the plunge installing the bootloader, 3.27 radio ROM and DCD 2.3.2 kitchen build on my XV6800. However, I didn't just go with the stock kitchen. I added a couple of additional OEM packages from Alex.Kaiser.v4.OEM.Packages (the nue LED and audioparam packages and Resco File Explorer 2007 in particular).
The updating went great and I was able to OTA reprogram my phone without needing to call Verizon. However, I noticed that something wasn't right.
First, my phone had no connection data onboard so the phone didn't know to dial #777 for a data link and my attempts to enter this manually didn't give me any success.
Second, my PC wouldn't see the device unless I deselected the "advanced network features" (or similar, I forget the exact wording) checkbox.
Third, I couldn't install CAB files. They'd terminate immediately with an "installation was unsuccessful" message.
Finally, once I was able to establish a connection to the PC, I could add and remove files from the device *only* from the PC. Attempts to delete files from the device itself were met with a file permissions error.
After playing around for a while trying every tweak I could think of, I tried using Resco Explorer and, after a few minutes, got a registration code error/warning message. This made me wonder if this package was the problem: preventing certain types of file access due to it being in a limited-functionality mode from lack of a proper reg code.
So, I rebuilt the ROM without it and now all is well! I'm loving the new dialer and comm manager as well as the active GPS (I've tested it only with Google Maps and GPSToday so far and it gets to within half a block). Not sure how well EV-DO Rev A is working yet. I tethered the phone and ran an online speed check, obtaining 1.2Mbps download but only 60kbps upload. It's possible this is related to my local coverage (Nyack, NY), so I'll try this again from a known-good Rev A area.
Anyway, just wanted to relay my experience in case it proved useful to anyone.
One other thing: I used PIM Backup to backup my data beforehand since my sycing is generally done on my work machine and I was doing the ROM updating from home. Upon restore, it wouldn't restore my email messages because it didn't find the corresponding account. So, it's important to note that this account info isn't backup up and that you first need to create the account before doing the restore step (making sure to name the account the same as before so that it matches up).
David
Hey guys:
Quick question. I've got a bunch of apps registered on my phone. Every time I flash a new ROM I need to reenter all of those serial numbers. I was looking at the UC customization threads to see if maybe I could just create a provisioning XML to create the appropriate registry entries automatically. Problem is don't think all the apps store their registration information in the registry.
So a couple questions:
1. I've found a good way to see registry changes (and thus figure out which keys I need to update), but I can't find the equivalent for the file system. Is there a tool that can take a snapshot of the file system on the phone, and then show diffs of the current file system with that snapshot? (That way I could figure out the additional files I'd need to copy over to make apps think they're registered.)
2. Is there another mechanism, other than registry and file system, that apps use to set themselves as registered? I couldn't think of anything... but then I'm hardly a hacker. (Even though... and correct me if I'm wrong... this is not technically hacking -- the serials are valid, I just don't want to reenter 10 of them every time I flash)
3. (And this probably belongs more in the UC thread): for some reason my provisionining file has no effect whatsoever. I've verified syntactical correctness of the file, and that cabarc can successfully create a CAB out of it. I've verified that the file is "installed" during the customization step. Yet, after a reset I see none of the changes specified in the provisionining xml. Any idea how I can debug this? Is there a log file that the config program leaves somewhere?
Thanks!
Hi all, I'm building an Spanish rom with manilla, with one of the latest niki shipped roms I found (HTC_SPA_2.09.412.1)
Thing is, I got most of things covered, but I'm having some issues...
First, I would want to put "pure_black" theme as the default theme, but WITHOUT going through OperatorPKG (so it doesn't need to restart, neither use twice the space it should". I've tried overwriting "Windows Mobile Green.tsk" with the file on \SYS\Base_Lang_0C0A_DPI_96_RESH_240_RESV_320, but when flashing and rebooting the color scheme was... awful green. Then I tried hex editing the name of the theme, but as there are parts on binary (unlike others I saw on other htc phones), the thing wouldn't even start...
Second is Advanced Network. I don't use it for anything. I've tried to remove it, but even if there's no file related to the program, and setted "Hide=1" (not exactly of course) on the registry (at HKEY_LOCAL_MACHINE\ControlPanel\Advanced Network) it doesn't seem to do anything.
And third and last... Anyone has found a way to convert OEMAPPS automatically into single packages? It's a mess of files, and I've searched but didn't find a working solution...
try to see this:
http://wiki.xda-developers.com/index.php?pagename=AutoRun
Hi
I have been cooking ROMs for a week or so now and all has been great. I can't recall making any major changes, but I now get the following when the phone does it's initial boot (and every boot after that)...
"The file 'poutlook' cannot be opened. Either it is not signed with a trusted certificate? or one of its components cannot be found..." And I can't do anything. i have searched but i have nothing found related to this problem
I am using (and have been using) IOLITE 20765 ROM and SYS and OEM 5.50.
I have made no major changes - I was testing other ROM's and SYS's, but I have reverted back to 20765 and I get this error - I never got this error on the other versions of ROM's and SYS's.
I have also redownloaded the files and created a new Kitchen folder to cook in...
Please can someone help???
DT
An update.
Redownloaded SYS, ROM, OEM and Kitchen 1.2b and started from scratch. It now works, so I am not sure what the heck I did to the other folders ...but I am sure glad it is functioning again
Can anyone tell me how to associate extensions with a program? any images I have defaults to opening them in the Camera app (not sure why) - I want them like before - except I am not sure what app the standard WM6.1 opens images in - can some one advise please?
Thanks
DT
d_train said:
...but I am sure glad it is functioning again
Click to expand...
Click to collapse
That's why we have HardSPL. Some cooked ROMs will not even boot. In those cases, take battery out, replace battery, turn phone on with camera button held down. This will drop phone into bootloader mode and allow a new ROM to be flashed.
Can anyone tell me how to associate extensions with a program? any images I have defaults to opening them in the Camera app (not sure why) - I want them like before - except I am not sure what app the standard WM6.1 opens images in - can some one advise please?
Click to expand...
Click to collapse
These associations are done in registry. For packages, you need to hunt through the kitchen for the registry and make the appropriate changes.
When I needed to change association for videos to TCPMP, the way I took was:
1) Snapshot of registry
2) Ran TCPMP. Made the association changes in its options.
3) Resnapshot registry.
4) Compare the changes.
5) Scan through the entire kitchen and find and substitute the registry keys in the RGU files and also .dat files
6) An alternative is to create a registry change, to be applied after the main ROM is built (or run at first bootup) like all the registry packages.
Total Commander is great for this. It allow search of strings of text within files in a folder and display all files with the search text. It also allows comparison of 2 files, and highlights the differences. Good luck. This is very time consuming.