Database Develop

Extended ROM - Some CABs don't Execute

I'm trying to customize a few Extended ROMs here and I'm running into some stubborn CABs. When installed manually, everything works fine. No warnings, no errors. Just click the CAB, let it do its thing, then click OK.
Put these same ROMs into an Extended ROM and hilarity ensues. Some will work, others will not and I don't know why. Any suggestions on what I might be missing will be greatly appreciated.

Quick question?
Are the CAB's signed, if not are you installing the 'signed' unsign CAB 1st .

Edit: Thinking more about this (and realising that the 1st thing you do is disable signing in your ROM's ) can you provide a little more info about the CAB's (maybe an offending CAB if the content is not private?).
I managed to replicate this issue with a CAB that had a warm reset as part of it's install process (seems to bork the autoexec batch process) and I have had a similar issue with a CAB that just contained some simple OMA in the _setup.xml.
John

yes, that's the point. But how to make any Unsigned CABs become Signed?

huangyz said:
yes, that's the point. But how to make any Unsigned CABs become Signed?
Click to expand...
Click to collapse
Without wanting to sounds facetious you sign them ;-)
You would use a private key to generate an Authenticode signature for the CAB (and maybe the apps inside if you need to) however you would still need to install the ROOT certificate into the code stores on your device. Or get your app signed by a 3rd party with a certificate that has it's ROOT already on the device (MS's MobileToMarket and things like that take care of this for ISV's that need it).
Once you have the ROOT cert on the device in the correct store signing is trivial, you either use SignTool.exe from many of the MS SDK’s or just use the GUI options if Visual Studio is your poison. All you need is an export of the PKF (Private key) and the password to the certificate.
In enterprises one of the 1st things people often do before giving Windows Mobile devices out to users is to install a ROOT certificate for the enterprise onto the device in both the code and transmission stores. This means from then on you can sign in-house apps and CAB’s and they behave as signed commercial apps and you can use features like internal signed SSL for ActiveSync etc. etc.
Don’t forget you can also do away with a lot of this by installing the HTC signed “Disable Certificates” CAB 1st and then the signatures are not checked on subsequent CAB’s, EXE’s or anything code related for that matter.

djwillis said:
huangyz said:
yes, that's the point. But how to make any Unsigned CABs become Signed?
Click to expand...
Click to collapse
Without wanting to sounds facetious you sign them ;-)
You would use a private key to generate an Authenticode signature for the CAB (and maybe the apps inside if you need to) however you would still need to install the ROOT certificate into the code stores on your device. Or get your app signed by a 3rd party with a certificate that has it's ROOT already on the device (MS's MobileToMarket and things like that take care of this for ISV's that need it).
Once you have the ROOT cert on the device in the correct store signing is trivial, you either use SignTool.exe from many of the MS SDK’s or just use the GUI options if Visual Studio is your poison. All you need is an export of the PKF (Private key) and the password to the certificate.
In enterprises one of the 1st things people often do before giving Windows Mobile devices out to users is to install a ROOT certificate for the enterprise onto the device in both the code and transmission stores. This means from then on you can sign in-house apps and CAB’s and they behave as signed commercial apps and you can use features like internal signed SSL for ActiveSync etc. etc.
Don’t forget you can also do away with a lot of this by installing the HTC signed “Disable Certificates” CAB 1st and then the signatures are not checked on subsequent CAB’s, EXE’s or anything code related for that matter.
Click to expand...
Click to collapse
I am NOT a software developer so, most of your opinions sound enigmatic to me except that the last one: put the HTC signed "Disable Cert" in the 1st place of the ext-rom config.txt.
Thanks very much! I'll try later on.

gamescan said:
I'm trying to customize a few Extended ROMs here and I'm running into some stubborn CABs. When installed manually, everything works fine. No warnings, no errors. Just click the CAB, let it do its thing, then click OK.
Put these same ROMs into an Extended ROM and hilarity ensues. Some will work, others will not and I don't know why. Any suggestions on what I might be missing will be greatly appreciated.
Click to expand...
Click to collapse
most problably you forgot to set some cab file to read-only before saving the extende-rom.check the cabs atrebutes and the config.text file while inside de program that you are using to edit the extended-rom.its not because they are not signed as long you got the cert .cab set to be the first to be installed.also cab files that require user input will not work.this is from experience, as posted above.

huangyz said:
I am NOT a software developer so, most of your opinions sound enigmatic to me except that the last one: put the HTC signed "Disable Cert" in the 1st place of the ext-rom config.txt.
Thanks very much! I'll try later on.
Click to expand...
Click to collapse
So, where did you found the signed Disable_Cert.cab?

faria said:
most problably you forgot to set some cab file to read-only before saving the extende-rom.check the cabs atrebutes and the config.text file while inside de program that you are using to edit the extended-rom.its not because they are not signed as long you got the cert .cab set to be the first to be installed.also cab files that require user input will not work.this is from experience, as posted above.
Click to expand...
Click to collapse
Sorry to ping an old thread - flogging to proceed immedietly after...
Being that this is a windows device, isn't there a flag that can be passed when executing the cab - like you can on a windows installer application? Similar to setup.exe -q or whatever you're trying to do. Some flags set the answers to yes, admin mode... you get the picture. Does the cab installer engine allow similar flags to get passed with the cab execution command?

In PPC, it calls wceload.exe to install and uninstall a cab.
As shown in http://msdn2.microsoft.com/en-us/library/ms926281.aspx , the only possible argument is to ask or not ask for destination, but no quiet mode.
How can you call wceload.exe manually at ExtROM installation may be a question.

How To : Get session based net access for Java Apps

The problem
You have a Java application that makes use of the internet, eg Opera Mini or Google Local Maps, and you are finding that whenever it wants access the net you get prompted with a Yes/No dialog to either allow or disallow it to go through. With Opera Mini, this would occur everytime you clicked on a link to goto another page and in Google Local Maps it would happen everytime you pressed a button to scroll the map. Obviously this gets very frustrating as it slows down your use of the application.
This method of permitting net access each time it is required is known as "Oneshot".
The solution
The other method is "Session" where users are only prompted once per run of the application. However, some ROMs don't have this option under the security settings in the Midlet Manager despite being a newer version.
After much experimentation by a number of users, including myself, we have managed to determine that the rofs_target.zip file found in \Application Data\Tao\intent can be overwritten with one from a ROM where the "Session" option was available and it will give you this option in the ROM you are currently using.
1) Copy the attached cab file to anywhere on your device.
2) Make sure that you are not currently running any Java apps and that Midlet Manager has been closed down.
3) Execute the cab file and wait for it to finish.
4) Start up Midlet Manager and tap and hold on any app icon and then choose Security. Under Net Access you should now see the option of "Session".
Notes
This has only been tested on Wizard ROMs where Tao-Group's intent Midlet Manager is included. Whether it works on other devices that also have the same Midlet Manager has not been determined but other users are certainly welcome to try. The only thing the cab file does is overwrite (or create if it doesn't exist) \Application Data\Tao\intent\rofs_target.zip. It does not touch the registry or any other system related files or folders. As such it shouldn't break anything major if it doesn't work. All you would have to do is delete that zip file.
Having only been a recent "discovery", this method of getting the Session option back isn't refined as of yet. Collectively, we went through at least 3 other ways of doing it first, involving more files and doing it manually, before we arrived at the current cab installation. We may delve deeper into the folder structure found in the rofs_target.zip file to find out which file contains the appropriate setting so that we can make the solution even more compact. As such, this will be an ongoing thread and this post will be updated to include any developments.
Thanks to BAKup, gilbreen, aron7awol, gamescan

A little more information on the options this CAB adds. On a clean install you will get the following options in the Tao Java MIDlet Manager:
Net Access: No, Oneshot, Session (Session is default)
Local Connectivity: No, Oneshot, Session, Blanket (Session is default)
App Auto Run: No, Oneshot, Session (Session is default)
Messaging: No, Oneshot, Session (Oneshot is default)
Multimedia Recording: No, Oneshot (Oneshot is default)
Now, if you already have MIDlets installed you may have to remove them and reinstall to get the new options to show up. Also, you will want to make sure that the MIDlet Manager is NOT running when you install the CAB. Best advice is to do a soft reset and then install the patch immediately on boot. If you're customizing your Extended ROM, then slap it in there.
NOTE: This patch only fixes the security settings issue with the MIDlet Manager. It does not add JPEG support.

Seems to work well enough on the Hermes.
Thanks

Hi newbe from the UK here...
I have a MDA Pro with T-Mobile with the same problem, tried the fix above, copied & installed successfully... but still as before: only "Oneshot" and "No" options!!!
This is driving me insane!
Any help appreciated!

Yey! It works now!!
Just had to uninstall and reinstall the MIDlets and voila!
Reread gamescan's message
Thanks very much to all

Excellent; it works perfectly on my T-Mobile MDA Vario II with Opera Mini.

Hermes with T-mobile UK WM6 update
I was using the cab on my device (T-mobile Vario II) when it was running WM5. Having applied the recent t-mobile WM6 update, I found that the cab refused to install (citing that it was not meant for my device).
Bad times.
However, managed to force it back onto my device by opening the cab in post #2 (java_session_fix_-_june_15_2006.cab) in winzip and extract the file 00cab172.001 from it. I renamed the extracted file as rofs_target.zip and manually placed it in the location in post #1 on the device (\Application Data\Tao\Iintent) - I kept the original one backed up just in case - it was substantially larger than the replacement so you never know.
And now, once again, I can tag applets as having session based net access again!
Good times!

T-Mobile MDA pro now works with sessions
Hi
I spent ages looking for a solution this is great, I use my MDA for Betfair and could not use Betfair mobile as it kept asking for permission every page update, now it just keeps refreshing prices every 5 seconds.
A huge thankyou...
Dave

Delete Unwanted Programs?

I am trying to delete programs that I believe I don't need. I use WiFi and do not have T-Mobile Internet Plan. Would I create a problem if I delete the following:
DAT MailTrigger
OZ Communications OM IM
T-Mobile HotSpot Login Utility
Thank you!

Are these in your Remove Program list? If not, you may not able to 'uninstall' these nicely.
What I suggest is that you may want to have a look on your Ext ROM, get all the CABS file there. Use some CAB managers, to open each of them and see where they have places the files and delete them. If things goes wrong, you can always have it installed since you already know which CAB is responsible for which.
Or, if you can affort a hard reset, reset your device and do not allow the Ext ROM to be install (e.g. soft reset your device after the security setup). Then, go into your Ext ROM and install the CAB files one by one, to identify the CAB files that you do/do-not want to install. This will give you a clean installation.

hanmin said:
Are these in your Remove Program list? If not, you may not able to 'uninstall' these nicely.
Ys, these are in my Remove Program list. They are loaded apps/software that is part of the T-Mobile total package. I did not load these using a CAB file. I guess I will just take a chance and remove them and see what happens. Like you said below I can do a Hard Rest if I need to. Thanks for your input. I do appreciate it.
TonynMI
Click to expand...
Click to collapse

I remove those apps if I remember too and since I've never had a need for their functionality, I've never had a problem because of uninstalling them. All you really gain, however, is a tiny bit of memory...which is probably why I usually don't remember to remove them.

Just completed removing the following:
Memory Available Before/After Removal: (Saved
DAT MailTrigger 3450/3624 (174)
OZ Communications OM IM 3624/3629 (5)
T-Mobile HotSpot Login Utility 3629/4052 (423)
Restart after removal and no problems.
Thanks for your responses.

Custom ROM from existing ROM

Hi,
I would like to customize a ROM for myself but i would need your advice...
Is it possible to use a ROM (Lets say NRG ROM 2.5), and to customize it (reg tweaks, MMS config, Exchange Server config with password set by default, install some cab and put the registration keys by default....) ?
If this is possible, is it hard to update it ? for exemple if NRG updates his ROM, i also want to be up to date with mine, is it easy to "synchronize", or reapply all previous actions without too much hassle ?
Do you have any links i should read to start a Kitchen ?
Thanks in advance

It might be worth having a search around for SASHIMI. It'll let you collect .cabs and .reg files etc and automate running then after youve flashed a new ROM.
if you figure out how your reg details are kept for each piece of software (in the registry or a file etc.), you can get it to reinstate them after flashing too.
You could DL the latest verion of a ROM, pull it apart and change whatever you like and then flash it to your phone but it'd be a pain for pain version.
Using sashimi, its also easy to update your setup when indiviudual apps and settings change, without needing to reflash your phone and then re-sync etc.
The way I see it, sashimi only really needs setting up the once and then given a tweak when something changes rather than needing to be re-done as with a ROM...the only down-side I can really find is it needs running after a hard-reset, whereas if you cook the changes in they wouldnt (so its no good for 'find or nuke my stolen phone' type apps).
I believe a lot of cooked ROMs include 'User Customization' (UC) which does a similar thing, but i havent used it myself.
Also, I may be wrong, but i think you could need certain details from the original chef before you can pull apart a cooked ROM too (i remember reading about file somewhere in your kitchen, memory fails me though)-and, of course, the chefs permission
Let us know what you try out.
'tunes

[Q] Interop-unlock Ativ S with latest software (8.1 Update 1 or later)?

Hi,
with all those Lumia posts I'm wondering if it is also possible to interop-unlock a Samsung Ativ S with the latest software (8.1 Update 1 or later) on it *without* a prior downgrade to 8.0 GDR2/GDR3. If it is possible please tell me how or where to find the answer (my search yielded no result so far).
With interop-unlock I mean accessing the 'full' file system and registry and having additional capabilities just like it was/is possible with 8.0 GDR2.
Thanks.

Unblock RPC (file called "Non-production errors.txt" in the Documents folder of the phone, if I recall correctly). There are now two options:
First option: use chamber hijacking.
* Move an app with ID_CAP_INTEROPSERVICES (I like to use HTC's silly "Converter" app; it should still be available on all devices, but other targets are more popular) to the SD card.
* Either sideload or unzip and copy the contents to the SD card an app that uses Samsung RPC to write to the registry. You may need to remove ID_CAP_INTEROPSERVICES from the app before sideloading.
* Use any of the several tools for app hijacking, or do it manually (remove the Hidden and System flags from D:\WPSystem, then rename D:\WPSystem\apps to something like D:\WPSystem\apps1, then delete the files from the install folder of the app that you're hijacking, then move or copy the files from the install folder of the app that uses RPC into the install folder of the app you're hijacking; don't forget to un-rename the apps folder afterward).
* Run the hijacked app; it should by the registry editor app you replaced it with instead, and you can now interop-unlock the phone.
Second option: Use @djamol's "Root Tool" app from the Store, or another app that can modify its own capabilities via SD card tricks.
* Install "Root Tool" from the store; it should show up in Search.
* Move it to the SD card if it wasn't installed there to start.
* Run the app, hit Help, and follow the instructions (several of them are similar to the manual instructions above, but at the end you have to move the app from SD back to Phone before the trick works).
Note that in either case, the EnableAllSideloading app won't work (technically BootstrapSamsung will, but you shouldn't use it since it assumes EnableAllSideloading will be used afterward). Microsoft basically removed the capability that EnableAllSideloading relies on.

Thanks for your reply! So basically the same way works with Ativ S that works with Lumia and you don't need the Samsung diagnosis tool anymore. You just need SamWP8 or a similar tool that uses Samsung RPC after unblocking RPC.
I'll give this a try on the next weekend(s). :good:

Yeah, basically just that. The diagnosis app no longer has the registry editor, and the steps needed to launch to a specific page in an app (such as the reg editor) are technically still possible but are identical to just installing an interop-based registry editor (via hacks), so do that instead.

GoodDayToDie said:
Yeah, basically just that. The diagnosis app no longer has the registry editor, and the steps needed to launch to a specific page in an app (such as the reg editor) are technically still possible but are identical to just installing an interop-based registry editor (via hacks), so do that instead.
Click to expand...
Click to collapse
But after is it possible to unlock all capabilities?

How to interop-unlock now?
Mattemoller90 said:
But after is it possible to unlock all capabilities?
Click to expand...
Click to collapse
I'm curious about that as well.
I tried the second option from (you) GoodDayToDie: It is not possible to use Samsungs Registry Editor component from Root Tool after following the instructions (moved app to SD, deleted the two files, moved stuff from HACK-subfolder to its parent, moved app to phone memory; file "Non-Production Errors.txt" exists in Phone\Documents -- BTW: Is the file name case-sensitive?). The general registry editor from Root Tool works, but with this one it is not possible to write several important keys (e. g. MaxUnsignedApps).
After this I tried the first option: I can successfully deploy CustomPFD (replacing Preview for Developers by hand or with CustomWPSystem). But what to do then?
I tried replacing Preview for Developers with SamWP8, but the app won't start then (getting "Loading ..." for about ten seconds then it closes); also tried commenting some capabilities of SamWP8 and repeating, but has no effect.
Deploying SamWP8 or IO Explorer using application deployment tool obviously fails because of missing interop capability.
This is a fresh and clean installation of WP 8.1 Update 2 now if it should matter.
Any further hints would be appreciated.

My Samsung died months ago (spontaneous hardware failure; I wasn't even hacking on it at the time) so I can't test Samsung-specific things anymore.
The steps as described (by both you and me* *should* work - I assume you rebooted the phone afterwards - so if it's not then I'm confused. The registry editor in Root Tool is mildly terrible and sometimes gives error messages when stuff actually works, but if it's really not working then I'm not sure what you do about that.
As for unlocking all capabilities, that's going to take a little work. The hack used by BootstrapSamsung unlocks one capability, and technically it could be applied to *all* the capabilities, but it changes the registry value type and loses a couple of NULL bytes at the end of the value every time you do it, which is potentially going to break things if you do it to all the capabilities / leave the capabilities in that state for long.
For what it's worth, if you're willing to hard-reset, the OemSettings.reg method mentioned in a few other threads should work too. It requires writing to a normally-unreachable part of the file system, but the Samsung RPCComponent class allows you to do this. I haven't tested it, though, and it does require a hard-reset.

Im interested in this too
If it does not work then what to do if im on 8.1 update already?
@up
AFAIK path is
Unblock RPC Functions proved easy. You just need to create an empty file:
Phone \ Data \ Users \ Public \ Documents \ Non-Production Errors.txt
Click to expand...
Click to collapse
Maybe that's why it didn't worked if you put it just in documents.
I just want to change black/white background-color and accent color in registry. That's all.
Regards

GoodDayToDie said:
My Samsung died months ago (spontaneous hardware failure; I wasn't even hacking on it at the time) so I can't test Samsung-specific things anymore.
Click to expand...
Click to collapse
Ouch, too bad. Would be really useful to have your helping hands on getting this done.
The steps as described (by both you and me* *should* work - I assume you rebooted the phone afterwards - so if it's not then I'm confused. The registry editor in Root Tool is mildly terrible and sometimes gives error messages when stuff actually works, but if it's really not working then I'm not sure what you do about that.
Click to expand...
Click to collapse
I did reboot.
Is there an app with a basic registry editor out there so I could at least change phone manufacturer like I could with Root Tool (Root Tool doesn't seem to be available in the store anymore)?
As for unlocking all capabilities, that's going to take a little work. The hack used by BootstrapSamsung unlocks one capability, and technically it could be applied to *all* the capabilities, but it changes the registry value type and loses a couple of NULL bytes at the end of the value every time you do it, which is potentially going to break things if you do it to all the capabilities / leave the capabilities in that state for long.
For what it's worth, if you're willing to hard-reset, the OemSettings.reg method mentioned in a few other threads should work too. It requires writing to a normally-unreachable part of the file system, but the Samsung RPCComponent class allows you to do this. I haven't tested it, though, and it does require a hard-reset.
Click to expand...
Click to collapse
I tried to use ROMRebuilder, but it just gave me "Failed " when tapping "Backup". But with full file system access I copied OEMSettings.reg zip-file out of the known C:\Windows subdir, extracted the .reg-file, appended all the unlock stuff, repacked and put it back to its original place overwriting the original file (with Root Tool, because in Windows Explorer I didn't have the right to write - Root Tool told me it was successful. I didn't double check ). But after resetting (About - Reset phone) no unlock or access to C:\ was there. Looks like the stock ROM. What went wrong..?
Edit: Used CustomPFD for registry access. Looking at "This PC\Samsung ATIV S\Phone\Windows\Packages\RegistryFiles\OEMSettings.reg" I can see that it is the original file, not my modified one. Is this file restored from somewhere upon reset or did my copy action fail?
Edit2: Tried using vcREG_1_2_BOOTSTRAP (replaced Extras & Info). It gives me an error about missing ID_CAP_INTEROPSERVICES, so it can't do anything.
And CustomPFD can't write MaxUnsignedApp. :-/

Not sure if ROMRebuilder is smart enough to use Samsung's RPC instead of Nokia's for moving the file into place, but regardless it requires interop itself (at least, I'm not sure how it could work otherwise). Root Tool definitely requires interop in order to overwrite Windows files, although it can do so. For the record, for stuff like just reading files or registry values, you can use the (normal-caps) version of my webserver; might be a bit easier.
vcREG should work, assuming it supports Samsung RPC - I think so, but I haven't checked - and you use the whole app hijacking thing correctly. Did you launch the hijacked app after the installation? Pretty sure Extras+Info has interop, so that *should* work.
EDIT: Assuming that the Samsung RPC service is working at all. I don't know of any easy way to test that short of just trying to do things with it, though. I don't think they "fixed" the RPC unblock, though...

GoodDayToDie said:
Not sure if ROMRebuilder is smart enough to use Samsung's RPC instead of Nokia's for moving the file into place, but regardless it requires interop itself (at least, I'm not sure how it could work otherwise). Root Tool definitely requires interop in order to overwrite Windows files, although it can do so. For the record, for stuff like just reading files or registry values, you can use the (normal-caps) version of my webserver; might be a bit easier.
Click to expand...
Click to collapse
Okay, so it probably didn't replace the file at all but only showed a success message. Grmbl. Which file manager would you recommend for moving the file to its place or in general?
vcREG should work, assuming it supports Samsung RPC - I think so, but I haven't checked - and you use the whole app hijacking thing correctly. Did you launch the hijacked app after the installation? Pretty sure Extras+Info has interop, so that *should* work.
Click to expand...
Click to collapse
Ohhh, you mean if I started the app that's about to be hijacked before actually hijacking it? No, I did not. (Not sure what Extras+Info would do on a Ativ S...)
But I do have to?
Edit: Removed Extras&Info (with dummy.xap), installed it again, started it (it actually works) and replaced it with vcREG_1_2_BOOTSTRAP.xap. Started vcREG, but it still gives me "error initializing. check if you have correct permissions (ID_CAP_INTEROPSERVICES). registry functions disabled".

I've also deployed CustomPFD and original preview for developers to sdcard. I have access to the registry but can't write values
Have you tried to hijack Extra+Info permissions with CustomPFD? It does not work with original PFD but it may work with Nokia one. I can't find Extra+Info xap to test, sorry.
Ok tried to deploy ROMRebuilder and hijack original PFD permissions. ROM Rebuilder just crashes on start (no message) WP 8.1 14157.

Installed ROMRebuilder with deleting Capabilities from xap and deployed it from deployment tool.
Manually removed PfD with SD hack and replaced it with ROMREbuilder.
It starts but when pushing "Backup" it says FAILED
Jesus im so tired with this phone...
ROM flasher does not work at 8.1 x64 even with test mode..

Ezio21 said:
Have you tried to hijack Extra+Info permissions with CustomPFD?
Click to expand...
Click to collapse
Yes I have. CustomPFD doesn't start in this case (it does when I'm replacing Preview for developers).

cerebos said:
Edit: Removed Extras&Info (with dummy.xap), installed it again, started it (it actually works) and replaced it with vcREG_1_2_BOOTSTRAP.xap. Started vcREG, but it still gives me "error initializing. check if you have correct permissions (ID_CAP_INTEROPSERVICES). registry functions disabled".
Click to expand...
Click to collapse
Your phone can't initialize Lumia RPC.

So what can we do?

What apps are there that use Samsung RPC to write to the registry? I know SamWP8 and IO Explorer. Any more?

@cerebos
Huh im sorry but it seems that only one way to get that Interop unlock is to flash GDR3

I flashed GDR3 but there is NO WAY to unlock your phone anymore. WP 8.0 developer registration is down. You can't install developer unlock helper and can't interop unlock your phone.
Also because of Samsung firmware update you can't install custom rom on wp8.0
How to interop unlock WP 8.0 without developer unlock? Any way? Or we're locked forever?
As far as I know you can still use beta apps on windows store. Is there anyone with personal developer account reading and could upload Interop_Unlock_Helper_Debug_ARM.xap as BETA to the store and send me the link? I would be very grateful (
@-W_O_L_F- maybe?
We're in very bad situation now. Thanks for any help or advices

Based on the Posting here (by @-W_O_L_F-) it looks like 8.1 Update 2 can't be interop-unlocked. So I'll need to downgrade first.
Edit: Assuming vcREG could write to Samsung Registry is only true for a small set of values, it is never true for interop-unlock. For this you need a registry editor with Samsung's RPC components.