Related
Hi Guy's,
Ive got a real simple question that im sure loads of people know the answer to (except me lol) I build ROMs for personal use but one thing ive never been able to get the answer to is how to get the region set to UK in a ROM, let me give you the latest senario.
Im using the latest Official WWE HTC WM6.1 ROM.
What i want to do is set the default regional settings to United Kingdom. So when you do a hard reset and the setup wizard appears, i want it to be set to the UK instead of the US.
Is there a way to do it in KaiserKitchen or some other tool or will i have to change the settings on my device then take a dump of that?
Ive searched all over for the answer but I cant find it, maybe it is there but im not entering the right sort of search query i dunno, just dont flame me coz i have searched lol.
Its in the registry:
Code:
[HKEY_LOCAL_MACHINE\nls]
"DefaultLCID"=dword:00000809
"SystemLCID"=dword:00000409
Set the DefaultLCID to 809 for the UK. When I dumped the official HTC ROM it was the Australian one and even though I was setting the above in a .rgu file in my kitchen it was being overwritten by a provxml file - mxipupdate_oemoperators_105.provxml.
I edited this file as follows:
Code:
<!-- Regional -->
<characteristic type="Registry">
<characteristic type="HKLM\nls">
<parm name="DefaultLCID" datatype="integer" value="2057"/>
</characteristic>
</characteristic>
The value '2057' is decimal for 0x809.
HTH
Andy
Sweet,
Thanks for the info, will try it out today.
Edit:
So if i undestand correctly, just changing "DefaultLCID" parameter to 2057 (Which i have now done in Kaiser Kitchen) should be enough right?
RavenY2K3 said:
Sweet,
Thanks for the info, will try it out today.
Edit:
So if i undestand correctly, just changing "DefaultLCID" parameter to 2057 (Which i have now done in Kaiser Kitchen) should be enough right?
Click to expand...
Click to collapse
Yes. Any .RGU registry files are used to create the initial default registry file, the 'provxml' files are parsed following a hard-reset so any registry ones overwrite the default values.
HTH
Andy
Hi
The problem/querry has sort of expanded now, although i changed the the detail in the provxml file, the change isn't reflected when the ROM is flashed it almost like no changes happen at all, any ideas? The expansion i speak about is id like to set the default carrier settings to T-Mobile UK, Ive put all the details in the "mxipupdate_oemoperators_101.provxml" not sure if this is the right file or the right way but it seemed to be the most file fitting file as other entries of this nature are in this file <characteristic type="CM_GPRSEntries"> for example.
Do i need to change some entries in Config.txt, Config_ap.txt or anything?
I know you can change these details by making a CAB file, but the only experience ive had with this is just re-packaging cabs that were already made etc... or if someone already knows the whereabouts of such a CAB could you pooint me in the right direction.
Ive made working ROMs with Alex's base ROMs before but never have i used an official ROM and more to the point, im wanting to leave quite a lot of it alone, I just want to add a couple of apps, change the region and set the Kaiser to TMO UK straight "out of the box"
It's really bugging me lol.
Any help at all would be great, thanx in advance.
RavenY2K3 said:
Hi
The problem/querry has sort of expanded now, although i changed the the detail in the provxml file, the change isn't reflected when the ROM is flashed it almost like no changes happen at all, any ideas? The expansion i speak about is id like to set the default carrier settings to T-Mobile UK, Ive put all the details in the "mxipupdate_oemoperators_101.provxml" not sure if this is the right file or the right way but it seemed to be the most file fitting file as other entries of this nature are in this file <characteristic type="CM_GPRSEntries"> for example.
Do i need to change some entries in Config.txt, Config_ap.txt or anything?
I know you can change these details by making a CAB file, but the only experience ive had with this is just re-packaging cabs that were already made etc... or if someone already knows the whereabouts of such a CAB could you pooint me in the right direction.
Ive made working ROMs with Alex's base ROMs before but never have i used an official ROM and more to the point, im wanting to leave quite a lot of it alone, I just want to add a couple of apps, change the region and set the Kaiser to TMO UK straight "out of the box"
It's really bugging me lol.
Any help at all would be great, thanx in advance.
Click to expand...
Click to collapse
Provxml deals withe the cid on initial startup, locale settings are changed in the registry(oem drivers or apps RGU)Connection setup should auto run on first power after customization that will autoconfig the device to t-Mo.
hi every body
would you like explain me for to translate reg_binary in provxml file?
because i want to change the default register
Hi,
I am using in my ROM the normal process to start the customization after burning the ROM.
File \OEM\OperatorPKG\mxipupdate_zzPIED_101.provxml:
<wap-provisioningdoc>
<characteristic type="Registry">
<characteristic type="HKLM\Comm" >
<parm name="AutoRunCFG" value="\windows\config_operator.txt" datatype="string" />
<parm name="AutoRun" value="\windows\AutoRun.exe" datatype="string" />
</characteristic>
</characteristic>
</wap-provisioningdoc>
In my config_operator.txt I am installing some CABs - which works fine.
My idea was to delete all CABs after installation automatically. For that reason I have changed a *.rgu under \SYS\Shell:
from
[HKEY_CLASSES_ROOT\cabfile\Shell\Open\Command]
@="wceload.exe \"%1\" /delete 1"
to
[HKEY_CLASSES_ROOT\cabfile\Shell\Open\Command]
@="wceload.exe \"%1\" /nodelete"
In normal cases @="wceload.exe \"%1\" /delete 1" makes sure the a CAB will be deleted after installation.
If I install a CAB after customization the CAB is gone - so far so good - means the entry in the registry is fine.
Unfortunately, during the customization (which works fine) the CABs are still under \windows. It seems that the above change does not work with customization.
Question:
Does the autorun process (during the customization) after burning a ROM also using the wceload.exe to install a CAB ?
Regards
kuzco1
I was going to ask a very similar question, but I think I'll just bump yours instead
'Burn' the ROM
Yes, really like it rather than 'flash'.
If u want the cab deleted after autorun, just remove the read-only attributes & vice-versa. (if cabs in SD)
/nodelete switch wont work as it still delete the cab if the cab is not with read-only attr.
i think autorun doesnt use wceload but let the experts confirm it first. Just my guess.
So you want to delete a file from the ROM during customization (wont work) or off the MicroSD (would work), however I don't think I would include something from the SD in the customization XML I would use an auto installer first.
Thanks
Wait, I'm sorry, but it looks like you've changed the registry to NOT delete the .cab
mbarvian said:
Wait, I'm sorry, but it looks like you've changed the registry to NOT delete the .cab
Click to expand...
Click to collapse
Heh...yeah I think he got those switched.
But, the point is.. when you cook a ROM, everything in that ROM gets flashed to the read-only part of your device's memory. It can't be deleted...through any (normal) means.
This is one of the reasons some people like lite-ROMS...because ROMs that have alot of stuff in them just can't have their contents manually deleted.
With the Kasier memory map at least there is no way to do this.
As suggested, you could have those CABs on the storage card, but that wouldn't be advised as those might not be present.
bengalih said:
Heh...yeah I think he got those switched.
But, the point is.. when you cook a ROM, everything in that ROM gets flashed to the read-only part of your device's memory. It can't be deleted...through any (normal) means.
This is one of the reasons some people like lite-ROMS...because ROMs that have alot of stuff in them just can't have their contents manually deleted.
With the Kasier memory map at least there is no way to do this.
As suggested, you could have those CABs on the storage card, but that wouldn't be advised as those might not be present.
Click to expand...
Click to collapse
OK thanks for that useful info bengalih
hmm, so I guess the best thing to do would be either cook it in, or go for a light approach. However, if going with the light approach, wouldn't the device perform worse than if the .cabs were cooked in an OEM package?
mbarvian said:
OK thanks for that useful info bengalih
hmm, so I guess the best thing to do would be either cook it in, or go for a light approach. However, if going with the light approach, wouldn't the device perform worse than if the .cabs were cooked in an OEM package?
Click to expand...
Click to collapse
As far as I know... the memory in the Kaiser is the same type, and is just separated into the read-only portion (where the ROM is flashed to), and the writable portion (where you can install content into).
This has been mentioned many times, and I don't think anyone has gotten any more conclusive than I had in some earlier threads about memory types on the kasier.
So, no... if you install App1.exe by cooking into your ROM, vs. installing it afterwards, there shouldn't be a difference in the speed. Obviously, if you install it to your storage card it will be slower.
I have always been a proponent of lighter ROMS, the reason being is not that I don't want a lot of stuff...I generally do load a lot.. But, the problem is it can't be removed.
So, if you cook in an app into your ROM, and that app is then updated you have to install the updated versoin without removing the original (which is cooked in and read-only). To make it worse, quite a few apps install things in the \Windows directory and won't even allow you to upgrade because it can't overwrite itself (or be installed to an alternate location).
My advice, especially if cooking for yourself is to cook in any core apps that are unlikely to get updated (like Office, basic games, etc.). Just cook in the files (e.g OEM packages) and not the CABs themselves.
Any other apps that you see as needing updates I would install separately, unless you want to be recooking the ROM every time you want to update them.
bengalih said:
As far as I know... the memory in the Kaiser is the same type, and is just separated into the read-only portion (where the ROM is flashed to), and the writable portion (where you can install content into).
This has been mentioned many times, and I don't think anyone has gotten any more conclusive than I had in some earlier threads about memory types on the kasier.
So, no... if you install App1.exe by cooking into your ROM, vs. installing it afterwards, there shouldn't be a difference in the speed. Obviously, if you install it to your storage card it will be slower.
I have always been a proponent of lighter ROMS, the reason being is not that I don't want a lot of stuff...I generally do load a lot.. But, the problem is it can't be removed.
So, if you cook in an app into your ROM, and that app is then updated you have to install the updated versoin without removing the original (which is cooked in and read-only). To make it worse, quite a few apps install things in the \Windows directory and won't even allow you to upgrade because it can't overwrite itself (or be installed to an alternate location).
My advice, especially if cooking for yourself is to cook in any core apps that are unlikely to get updated (like Office, basic games, etc.). Just cook in the files (e.g OEM packages) and not the CABs themselves.
Any other apps that you see as needing updates I would install separately, unless you want to be recooking the ROM every time you want to update them.
Click to expand...
Click to collapse
wow, another good post
that is basically what I am trying to accomplish. I have my registry tweaks, files that don't get updated (Office, etc.) cooked in, but for some reason I cannot change the look of the dialer (I wanted to use poorlyduck's diamond dialer) by converting it to an OEM package with Ervius' Package Creator. Same with the comm manager skin. Therfore, I have resorted to installing these two through their default cabinet files during initial customization.
also, here's some very nice posts by duttythroy in the diamond rom development concerning this topic:
duttythroy said:
Just a tip, A clean rom is very good if you going to stick with what you got in the rom and possible a few otther apps by cabs, If your going to installed the same apps which are in a full rom then the clean rom with those apps in will make you lose valuable storage space rather than them cooked in and sometimes device will start to feel sluggish but it all depends on how many cabs youre going to re-install.
TIps , there are certain apps which are cooked in doesnt take up any storage space but if install by cab you will then use up valuable space.
Click to expand...
Click to collapse
duttythroy said:
bascally there some programs which ar cooked in for e.g Remote desktop, If cook this in its 1.45mb I think, I will only use up only about .45mb and save 1mb of storage space, If i install this by cab I would use up all of the 1.45mb storage space
Click to expand...
Click to collapse
mbarvian said:
wow, another good post
....
also, here's some very nice posts by duttythroy in the diamond rom development concerning this topic:
Click to expand...
Click to collapse
Well dutty is by far a better cook than I... I'll stick to the scripting. I understand the basics of cooking...I just don't have the temperment for it.
However, I don't fully agree with all those points. I think his conclusions are correct, but I don't think the reasoning behind them are.
First off with space. Windows machines (be they PCs or WM devices) are basically made up of two things. File system and Registry (the registry just being a special file on the system). If I remove 2MB worth of an app from a ROM before I cook it, and then create a .CAB that contains those 2MB of files, the same amount of space is going to be taken up.
I have ripped quite a few apps to compile CABS from ROMs, and I know this to be the case.
So, in theory there is no reason why an app that is cooked into the phone would take up any less space than a .CAB. The only additional thing that the .CAB would create is a registry entry that the .CAB is installed.
In practice however, dutty may be correct. Because it is very difficult to figure out where everything is and strip it properly from a ROM. So, you might think you ripped out App1, but in reality you left a couple of extra files in the Windows directory, or a few registry keys, etc. Generally if there is a space discepancy beyond a very small amount (a couple reg entries perhaps) then the cook doing the cleaning or the person packaging the CAB probably weren't as thorough as they could be.
Another possibility is that some apps that may reside in the windows directory on a loaded ROM share some common files. If you attempt to install this via CAB to a separate directory, you may need to duplicate some files. But again, this is how you go about the work, so if done right and clean the space difference should be negligible.
The other point regarding speed of cooked in vs. installed. I don't think things are going to get sluggish one way or the other. Again, this is in theory. In practice, cooks often mess things up when they are in there tinkering with a ROM. If I rip out AppA and make a CAB out of it and then say the CAB performs sluggishly whereas it was fine when it was cooked in...well then the CAB probably was ripped wrong!
This is very much not an science but an art (sometimes to my dismay!). And there definitely isn't alot of controlled scientific basis for alot of what floats around out here.
Again, in practice many of these issues happen, so I think dutty's points are valid...but I think they can be avoided with precision work.
EDIT: I suppose some greater space savings could be had if the cooked in apps had some sort of memory compression. Although as far as I know this doesn't exist on the Kaiser. And, even if they were saving space due to compression in the memory, that would only serve to decrease performance (higher compression = slower performance).
bengalih said:
So, in theory there is no reason why an app that is cooked into the phone would take up any less space than a .CAB. The only additional thing that the .CAB would create is a registry entry that the .CAB is installed.
In practice however, dutty may be correct. Because it is very difficult to figure out where everything is and strip it properly from a ROM. So, you might think you ripped out App1, but in reality you left a couple of extra files in the Windows directory, or a few registry keys, etc. Generally if there is a space discepancy beyond a very small amount (a couple reg entries perhaps) then the cook doing the cleaning or the person packaging the CAB probably weren't as thorough as they could be.
Another possibility is that some apps that may reside in the windows directory on a loaded ROM share some common files. If you attempt to install this via CAB to a separate directory, you may need to duplicate some files. But again, this is how you go about the work, so if done right and clean the space difference should be negligible.
The other poing regarding speed of cooked in vs. installed. I don't think things are going to get sluggish one way or the other. Again, this is in theory. In practice, cooks often mess things up when they are in there tinkering with a ROM. If I rip out AppA and make a CAB out of it and then say the CAB performs sluggishly whereas it was fine when it was cooked in...well then the CAB probably was ripped wrong!
This is very much not an science but an art (sometimes to my dismay!). And there definitely isn't alot of controlled scientific basis for alot of what floats around out here.
Again, in practice many of these issues happen, so I think dutty's points are valid...but I think they can be avoided with precision work.
EDIT: I suppose some greater space savings could be had if the cooked in apps had some sort of memory compression. Although as far as I know this doesn't exist on the Kaiser. And, even if they were saving space due to compression in the memory, that would only serve to decrease performance (higher compression = slower performance).
Click to expand...
Click to collapse
can't argue with this post
mbarvian said:
Wait, I'm sorry, but it looks like you've changed the registry to NOT delete the .cab
Click to expand...
Click to collapse
hi,
yes you are right .. I have done the other wy. My fault in my first post. I have changed /nodelete to /delete.
But anyway, I understood that it is not possible to delete cabs during customization.
Many thanks to all
kuzco1
Installed NueLED and after finding out it doesn't work for me I got rid of it almost completely. The only thing I seem to have left behind is one registry key: HKEY_LOCAL_MACHINE/Drivers/BuiltIn/nueLED which I'm unable to remove in both MemMaid and Resco Registry. I managed to remove every single item in that key and even tried to rename it, no cigar. Actually, instead of renaming the key it created a new key with a new name, which I cannot remove either. Strange stuff. The device works alright, but this thing just bugs me. WM6.
krypton22 said:
Installed NueLED and after finding out it doesn't work for me I got rid of it almost completely. The only thing I seem to have left behind is one registry key: HKEY_LOCAL_MACHINE/Drivers/BuiltIn/nueLED which I'm unable to remove in both MemMaid and Resco Registry. I managed to remove every single item in that key and even tried to rename it, no cigar. Actually, instead of renaming the key it created a new key with a new name, which I cannot remove either. Strange stuff. The device works alright, but this thing just bugs me. WM6.
Click to expand...
Click to collapse
If you can't delete, then there is a reason! Perhaps you should leave it alone, before you possibly cause some damage. If it bugs you that much, just hard reset.
I also want to know that..and I'm so thankful that I'm here in this site.
TheChampJT said:
If you can't delete, then there is a reason! Perhaps you should leave it alone, before you possibly cause some damage. If it bugs you that much, just hard reset.
Click to expand...
Click to collapse
Well, I just cannot think of any reason why I shouldn't be able to delete a key I myself created and therefore it's useless (now I'm talking abou tthe "renamed" one). As for the original NueLED key, it should be safe too as it's specifically mentioned in the NueLED thread as a part of manual uninstall procedure.
My bad in advance if this question is off topic.
Lets you say you flashed the stock rom [why i don't know] or one of the roms hanging around here. The RUU goes to 100%, you set the screen, the time, you get a peek at the home screen (lookin pretty plain there) only to be told to wait 3 seconds. A couple things run get a little progress indicator and the thing reboots.
Now your home screen is looking different. Couple plugins enabled, others disabled. Been scouring XDA regarding this and only found scant references here or there about setting your thing up to install cabs off an SD card. I'm looking for something more in the neighborhood of having different plugins enabled, possibly settings too.
Anywho if you know of where I can get some reading in about this type of stuff, lemme know.
It's the built-in autorun. There are also many different third party alternatives. A few are in SuperJustKitchen v0.7.
Besides that, I'm trying to decide if this is offtopic or not... Technically it has to do with cooking....
ivanmmj said:
It's the built-in autorun. There are also many different third party alternatives. A few are in SuperJustKitchen v0.7.
Besides that, I'm trying to decide if this is offtopic or not... Technically it has to do with cooking....
Click to expand...
Click to collapse
hehe i'm walking a fine there...
I was wondering who were those guys and what are they doing in my kitchen? Autorun, check autorun, and run cc From what I gathered about those programs is that runcc is like autorun but newer. My guess in using them is setting up some sort of txt file and pointing runcc or autorun to it.
If so what can I put in that txt file, coz I know i can't write something like "uh... dood, I don't want titanium enabled, I want this one enabled with this setting and that setting ticked... and while you're at it can you fiddle with that one over there, and lets throw some cabs on there shall we? they're over here..... you're not done yet, now I want you to monkey with the settings like so... alright now get the hell out of my office!"
If I could I would...
Whatever information you can point me over to would be cool.
Thanks
Dr.Gonz0 said:
hehe i'm walking a fine there...
I was wondering who were those guys and what are they doing in my kitchen? Autorun, check autorun, and run cc From what I gathered about those programs is that runcc is like autorun but newer. My guess in using them is setting up some sort of txt file and pointing runcc or autorun to it.
If so what can I put in that txt file, coz I know i can't write something like "uh... dood, I don't want titanium enabled, I want this one enabled with this setting and that setting ticked... and while you're at it can you fiddle with that one over there, and lets throw some cabs on there shall we? they're over here..... you're not done yet, now I want you to monkey with the settings like so... alright now get the hell out of my office!"
If I could I would...
Whatever information you can point me over to would be cool.
Thanks
Click to expand...
Click to collapse
RunCC is meant as a replacement for Autorun. Autorun just requires a text file while RunCC requires a Lua that points to a text file.
There are a few walkthroughs but nothing concrete on how to create a good autorun file.
Some of the commands are:
The lock screen command (I forget what it is)
EXEC: (Execute the following)
CAB: (Install the following cab)
CPY1: (Copy from this)
CPY2: (Paste to this)
RST: (reset the phone)
In the older Autoruns, to set a theme you'd use:
EXE: along with a program that set the theme
In the newer Autoruns, you can just set it with:
TSK: \Windows\theme.tsk
Unfortunately, neither works with WM6.5.1 so you have to set the theme with an EXT with many files and registry keys.
There are a few other autorun apps that people in xda have made that can do more, like be able to run your own custom config from your SD card if you want every ROM to have certain things automatically configured (as long as all the ROMs support the particular auto-configuration utility you have configured for.)
To tell you the truth, I never bothered much with Autorun unless I had to replace a file that needed to be one version for the rom to load the first time and another after the first time set up was done. Realistically, you can do almost everything with a simple EXT package.
ivanmmj said:
Unfortunately, neither works with WM6.5.1 so you have to set the theme with an EXT with many files and registry keys.
Click to expand...
Click to collapse
Now ain't that a kick in the pants
ivanmmj said:
To tell you the truth, I never bothered much with Autorun unless I had to replace a file that needed to be one version for the rom to load the first time and another after the first time set up was done. Realistically, you can do almost everything with a simple EXT package
Click to expand...
Click to collapse
I was thinking the very same thing. Something's telling me that I need to try out that "Create Ext" button. Maybe throw whatever reg keys I want played with in that file? That would be more simpler than creating an auto run thingie. Hmmm... if that is the case I guess I would to just need to know how to tinker with my home screen and settings from the registry.
Dr.Gonz0 said:
Now ain't that a kick in the pants
I was thinking the very same thing. Something's telling me that I need to try out that "Create Ext" button. Maybe throw whatever reg keys I want played with in that file? That would be more simpler than creating an auto run thingie. Hmmm... if that is the case I guess I would to just need to know how to tinker with my home screen and settings from the registry.
Click to expand...
Click to collapse
The easiest way to learn is to take a CAB that does something you like and converting into a EXT and looking at the registry settings it creates.
ivanmmj said:
The easiest way to learn is to take a CAB that does something you like and converting into a EXT and looking at the registry settings it creates.
Click to expand...
Click to collapse
That definitely helps, as well as using a reg editor to find out what has been done after installing a program then exporting the key to throw in the app.reg file. The real fun part was tracking down basic settings for things like button settings, today items (and their settings), and default theme (boy was that a blast!) Thanks again for clearing up the confusion
Hi,
Something weird happened to my phone, all of my side-loaded apps were suddenly throwing this error, weird thing is that I did not even connected it to my PC (Zune) the whole day.
Upon searching similar threads, seems my phone was relocked again. My question is, is there any way to unlock it again without downgrading to NoDo (phone has Mango B2 7720.68)? If I opt to go back to NoDo and perform the unlock again, then upgrade again to Mango B2, will I encounter the same (hope anyone can confirm)?
Does any one experiencing the same today? Or maybe just my unlucky day today.
Thanks.
nohctis said:
Hi,
Something weird happened to my phone, all of my side-loaded apps were suddenly throwing this error, weird thing is that I did not even connected it to my PC (Zune) the whole day.
Upon searching similar threads, seems my phone was relocked again. My question is, is there any way to unlock it again without downgrading to NoDo (phone has Mango B2 7720.68)? If I opt to go back to NoDo and perform the unlock again, then upgrade again to Mango B2, will I encounter the same (hope anyone can confirm)?
Does any one experiencing the same today? Or maybe just my unlucky day today.
Thanks.
Click to expand...
Click to collapse
Same here about an hour ago.
I think the phone has become chevron locked.
I have tried sending unlock.cab in mango and it installed correctly, did a vol+- reset. But no joy.
I think it needs a settings/about reset, but this will ruin my set-up (took me a day last time, though should be quicker next time)
Anyone care to confirm needing reset?
As an aside I think I've gone over Zune's 5 phone limit (settings/accounts/devices) since my apps weren't loaded to phone last time and I had to load them manually. Even though only one phone (first yuki nodo rom) showed up on the bottom list. I deleted it and now may have to wait 30 days before synching apps again.
Edit; sorry, I am in the wrong forum (found by search). But may still be relevant
This is scary...can MS relock unauthorized unlocks OTA? What were you doing when it "relocked" and did you unlock as dev or chevron?
The other thing is you need Interop-Unlock for sideloaded apps to run. Did you have your phone interop-unlock beforehand (i.e. Max Unsigned Apps reg edit)? Just having a Dev or Chevron unlock is not enough. But then you should have never been able to run these apps on Mango.
Yes, search the forum for the prevent re-lock registry hack...
drkfngthdragnlrd said:
Yes, search the forum for the prevent re-lock registry hack...
Click to expand...
Click to collapse
Ah, now I understand what that reg edit does! I know it unlocks the phone but it also redirects so I assume this prevents it from "phoning home" to the mothership...
LiFePo4 said:
Ah, now I understand what that reg edit does! I know it unlocks the phone but it also redirects so I assume this prevents it from "phoning home" to the mothership...
Click to expand...
Click to collapse
Exactly, it's not MS doing it actively. It's the phone/zune using those URL's to check if the device ID is listed as a current unlocked device.
thanks for the replies.
I used the CustClear.provxml method, the one that you need to run the htc connection when you're already in Mango B2.
Just a background;
1. My phone is from unlocked NoDo using the CustClear.provxml method also
2. With installed Advanced Config and checked the "Prevent phone from relocking" tweak.
3. Before upgraded to Mango B2, CustClear.provxml was placed again in Windows root
4. Upgraded to Mango B2 then run the htc connection
5. Already been using Mango B2 for 1 month (syncing and installing apps even homebrew), and not experiencing relock. So I'm in a assumption that it's really tweaked to prevent to relock
Then suddenly, it relocks yesterday eventhough I'm not even connecting my phone to Zune or to any PC the whole day.
I will try to open the exact file to see if there is really a prevent unlock registry included in the file when I get home.
right now I'm back to NoDo, can't live to not use my daily apps.
okay.. here's the actual content of my provxml
<wap-provisioningdoc>
<!-- *** COMMENTO *** -->
<characteristic type="Registry">
<characteristic type="HKLM\Comm\Security\LVMod">
<parm name="DeveloperUnlockState" value="1" datatype="integer" />
</characteristic>
<characteristic type="HKLM\Software\Microsoft\DeviceReg">
<parm name="PortalUrlProd" value="" datatype="string" />
<parm name="PortalUrlInt" value="" datatype="string" />
</characteristic>
<characteristic type="HKLM\Software\Microsoft\DeviceReg\Install">
<parm name="MaxUnsignedApp" value="2147483647" datatype="integer" />
</characteristic>
</characteristic>
</wap-provisioningdoc>
seems it contains the entry for prevent relock.. does it mean MS really relock my phone via OTA and bypassed that registry hack?
nohctis said:
okay.. here's the actual content of my provxml
<wap-provisioningdoc>
<!-- *** COMMENTO *** -->
<characteristic type="Registry">
<characteristic type="HKLM\Comm\Security\LVMod">
<parm name="DeveloperUnlockState" value="1" datatype="integer" />
</characteristic>
<characteristic type="HKLM\Software\Microsoft\DeviceReg">
<parm name="PortalUrlProd" value="" datatype="string" />
<parm name="PortalUrlInt" value="" datatype="string" />
</characteristic>
<characteristic type="HKLM\Software\Microsoft\DeviceReg\Install">
<parm name="MaxUnsignedApp" value="2147483647" datatype="integer" />
</characteristic>
</characteristic>
</wap-provisioningdoc>
seems it contains the entry for prevent relock.. does it mean MS really relock my phone via OTA and bypassed that registry hack?
Click to expand...
Click to collapse
Weird, maybe they "fixed" that hack in Mango. This would be the first I'm hearing of it though. Would make since with the new official Chevron Unlock coming soon.