Related
I have LUMIA 620 dev unlocked via dream spark.
I downloaded XAP file from marketplace and it seams to be encrypted so they are not installing via DEV tools to my device.
But i searched around some apps which can be installed via DEV tool because the are modified and i want to know what are the changes that are need to be made in XAP files:good:
One thing i have noticed that those XAP files which can be installed on device via DEV can be opend via any archive software like winrar etc...
but those XAP that are not able to install on device via DEV cannot be open with any archive software.
prashantvrm said:
One thing i have noticed that those XAP files which can be installed on device via DEV can be opend via any archive software like winrar etc...
but those XAP that are not able to install on device via DEV cannot be open with any archive software.
Click to expand...
Click to collapse
The XAP files from the store are encrypted. Unless someone figures out a way to break the encryption, it cannot be done.
The XAP files you found are probably home-made apps, which can be sideloaded, because they're deployed by developer tools in an unencrypted format, or WP7 apps. The encryption is applied after you submit the XAP to the store.
There is no known workaround to sideload store XAPs without an SD card, at the moment.
TheGoldrocker said:
The XAP files from the store are encrypted. Unless someone figures out a way to break the encryption, it cannot be done.
The XAP files you found are probably home-made apps, which can be sideloaded, because they're deployed by developer tools in an unencrypted format, or WP7 apps. The encryption is applied after you submit the XAP to the store.
There is no known workaround to sideload store XAPs without an SD card, at the moment.
Click to expand...
Click to collapse
You are correct sir. It sucks that you can't even sideload Xaps that were downloaded manually due to the app being removed from the WP store on a non-SD device. I'm trying to see if I can make a workaround for this though. It would be nice if it worked. In terms of modifying the encrypted XAP, it'll be a while before one of us figures out how to decrypt, but at the same time that opens a whole new can of worms regarding to piracy.
I've looked at the encrypted XAPs a bit myself; they're basically a PlayReady wrapper around the ZIP archive (XAPs are just renamed ZIP files; I usually use 7-Zip to open them). Unfortunately, I don't think anybody has broken PlayReady yet. The various programs which claim to strip PlayReady (usually from music or video) all appear to work by running the file through the decoder built into various programs like Zune and Windows Media Player, and re-capturing the content that comes out of the decoder. That won't work for these files.
We might be able to do something similar if we can get the XAP decoder out of the phone ROM and use that, though it will be ARM code (I don't know if the x86 "emulator" image includes the DRM decoder) and therefore somewhat tricky to work with. It will also probably be obfuscated to deter reverse engineering, and may be difficult to make work independently. A kernel debugger on the phone may be needed to figure it out.
GoodDayToDie said:
I've looked at the encrypted XAPs a bit myself; they're basically a PlayReady wrapper around the ZIP archive (XAPs are just renamed ZIP files; I usually use 7-Zip to open them). Unfortunately, I don't think anybody has broken PlayReady yet. The various programs which claim to strip PlayReady (usually from music or video) all appear to work by running the file through the decoder built into various programs like Zune and Windows Media Player, and re-capturing the content that comes out of the decoder. That won't work for these files.
We might be able to do something similar if we can get the XAP decoder out of the phone ROM and use that, though it will be ARM code (I don't know if the x86 "emulator" image includes the DRM decoder) and therefore somewhat tricky to work with. It will also probably be obfuscated to deter reverse engineering, and may be difficult to make work independently. A kernel debugger on the phone may be needed to figure it out.
Click to expand...
Click to collapse
It would be nice to be able to put one on the emulator itself and see what was going on..
I offer up my Programs folder dumped from my Lumia 928 if it is any help. Devs do with it as you will At the very least under common files you will find the xaps installed on my device which do open with 7zip and include the license xml. As far as installing or side loading I did throw a few xaps at the various emulators with mixed results. Have at it guys!!!
http://sdrv.ms/13tlc0F
tonbonz said:
I offer up my Programs folder dumped from my Lumia 928 if it is any help. Devs do with it as you will At the very least under common files you will find the xaps installed on my device which do open with 7zip and include the license xml. As far as installing or side loading I did throw a few xaps at the various emulators with mixed results. Have at it guys!!!
http://sdrv.ms/13tlc0F
Click to expand...
Click to collapse
Xaps within the Programs directory from a ROM are unencrypted. These will help out a lot though!
Edit: Ohhh... Something interesting. CommonFiles\Xaps\SyncUi.xap is the Verizon Backup Assistant. This has some code to intercept SMS..
<Extensions>
<!-- Email & Accounts UX Integration -->
<Extension ExtensionName="Accounts_Extension_Standard" ConsumerID="{47998C28-3D90-11E1-8E07-8B2B4924019B}" TaskID="_default" ExtraFile="Extensions\Extras.xml" />
<Extension ExtensionName="SMS_INTERCEPT_STANDARD" ConsumerID="{55DB4873-5CDF-43B0-82B4-87EB13E9BF6B}" TaskID="SmsInterceptAppExtension" ExtraFile="Extensions\Extras.xml" />
<Extension ExtensionName="Service_Agent_Application" ConsumerID="{208558CC-4407-40F8-83AE-AE3D567126B3}" TaskID="BackgroundTask" />
</Extensions>
snickler said:
Xaps within the Programs directory from a ROM are unencrypted. These will help out a lot though!
Edit: Ohhh... Something interesting. CommonFiles\Xaps\SyncUi.xap is the Verizon Backup Assistant. This has some code to intercept SMS..
<Extensions>
<!-- Email & Accounts UX Integration -->
<Extension ExtensionName="Accounts_Extension_Standard" ConsumerID="{47998C28-3D90-11E1-8E07-8B2B4924019B}" TaskID="_default" ExtraFile="Extensions\Extras.xml" />
<Extension ExtensionName="SMS_INTERCEPT_STANDARD" ConsumerID="{55DB4873-5CDF-43B0-82B4-87EB13E9BF6B}" TaskID="SmsInterceptAppExtension" ExtraFile="Extensions\Extras.xml" />
<Extension ExtensionName="Service_Agent_Application" ConsumerID="{208558CC-4407-40F8-83AE-AE3D567126B3}" TaskID="BackgroundTask" />
</Extensions>
Click to expand...
Click to collapse
I don't like the sound of that The app is part of the settings on my device but when opened says there is a problem with my account and contact Verizon.
@tonbonz: Thanks for the dump! That could be really handy. I'll explore and see if I can find anything useful. Any direct applications will likely be Nokia-specific (which among other things means I can't test them) but lots of people have Nokia phones, and I may find something more generally useful too.
GoodDayToDie said:
@tonbonz: Thanks for the dump! That could be really handy. I'll explore and see if I can find anything useful. Any direct applications will likely be Nokia-specific (which among other things means I can't test them) but lots of people have Nokia phones, and I may find something more generally useful too.
Click to expand...
Click to collapse
I've enjoyed the benefits of all the devs and their hard work here at XDA since my HTC Trophy. Glad to give back in any way I can. If any other files or folders are needed I would be happy to oblige...and... I thank you sir!!!
Oh what the h*** Rest of the dump files currently uploading. Dump 1, three 7z files altogether, is the Programs folder from earlier post. Left out maps data from Data/shared data folder as it was huge and of no consequence as to what we are trying to accomplish. Also, to be clear, this is a dump from the Lumia 928 variant package not my actual device. Have fun!!!
http://sdrv.ms/13tlc0F
@djtonka Thank you for your tutorial on Nokia Care Suite on wimdowsmania.pl.
@AnDim Extra thanks for ImgMount Tool which was used to dump these files!!!
I'll let you know. Just for curiosity's sake, how are you extracting those files? Is it from a working device, or a ROM image?
EDIT: Just saw your message, thanks for the info!
Initial results are a mix of cautious hope, disappointment, and speculation.
1) The OEM apps use a ton of restricted capabilities (among the most tame, for example, is "ID_CAP_MEDIALIB_PHOTO_FULL", which gives direct access to the image folders and has visibility "public" according to the policy XML files from the Windows directory).
2) The OEM apps can be sideloaded, but you have to remove the PlayReady header and all the restricted capabilities. They aren't very exciting at that point; they may not even start up.
3) Speculation: The so-called "public" restricted capabilities require a (Store-?)signed app when used on a standard phone. It *may* be possible to sign the apps ourselves, install that cert on the phone, and then sideload them, but I doubt it.
4) More speculation: These new, high-privilege capabilities seem to have largely replaced ID_CAP_INTEROPSERVICES. Although the error when trying to sideload them on an interop-locked phone is different than it is for INTEROPSERVICES, it may be that an interop-unlock would allow sideloading apps that use those capabilities anyhow.
5) The OEM apps include WPInteropManifest.xml. It's exactly the same near-empty file as on WP7. However, they don't use COM but instead use the same native-CLR interop as the official SDK advocates (.winmd files that bridge managed code to C++ DLLs). Its presence does not impede sideloading.
6) Speculation: The WPInteropManifest may be needed for apps which intend to use the "raw" win32 API (as opposed to WinRT) in C++. This theory is supported by the presence of things like DLLs that read and write to the registry directly (not through a driver, which would need INTEROPSERVICES), using APIs such as RegCreateKeyW.
7) More speculation: Since we can extract the system libraries from our phones, it should be possible to use the DLL-to-LIB tools to create .LIB files (the official WP8 SDK is extremely short on these) that we can then use to link to the native Win32 API. Although we would still be (cripplingly) limited by the sandbox's low permissions, we could probably do things like write a basic registry browser.
8) The provxml commands to install apps are very simple, but I don't understand all the parameters. Nonetheless, whenever we have an app, its license, and a tool which can process AppInstall provxmls, we should be able to install those apps on any reasonably compatible phone.
9) Speculation: Due to the use of OS-based capabilities rather than OEM drivers, an app that is installed on any given phone *should* work on other OEMs' phones even if it accesses the registry or does similarly privileged operations.
10) There may yet be a vulnerable app which we could exploit (possibly by using a provxml-injection attack?) to write to the registry / move files / do similar stuff. However, it would probably have very limited permissions even so; unlike on WP7, most things which can write to *some* of the registry can't write to *most* of it.
GoodDayToDie said:
Two problems with that.
First of all, the app's install directory is read-only to the app permissions. You can't create, delete, or modify any file there from within the app (without some sort of "jailbreak" at least).
Second, and possibly more importantly, the permissions sandbox (or "appcontainer") that the phone uses to restrict an app is created at app install. Modifying the manifest is unlikely to have any benefit whatsoever (it certainly didn't help on WP7).
A good idea, though. Always glad to see people checking for such things.
Click to expand...
Click to collapse
As wp8.1 allows to move an app to the sd-card, I think point one should be ok. So how about modifying the app? I plugged my sd-card to the pc but all app files are kind of encrypted..
I tried it with @GoodDayToDie Webserver 0.5.0. http://1drv.ms/1flmBN4
thanks
gipfelgoas said:
As wp8.1 allows to move an app to the sd-card, I think point one should be ok. So how about modifying the app? I plugged my sd-card to the pc but all app files are kind of encrypted..
I tried it with @GoodDayToDie Webserver 0.5.0. http://1drv.ms/1flmBN4
thanks
Click to expand...
Click to collapse
as my phone doesn't support SD Card please send me one of does little apps you moved to sd card (please send a free app to me)
I will check it
but if you want to try adding Capabilities to app then re-write it in the folder it's surely not possible .
application capabilities are all checked and stored in your phone exactly when you install them (from your pc using Developer Unlock or from store)
Le Sigh...
This has been discussed extensively long, long ago. The manifest is only parsed at installation. You can do whatever you want to the manifest afterwards; it doesn't seem to have any effect.
It wouldn't help much anyhow. You wouldn't be able to *launch* a sideloaded app with Interopservices if not interop-unlocked. This can be tested by interop-unlocking a phone, sideloading an interop app, resetting the MaxUnsignedApp value to undo the unlock, and trying to run the app.
Hey Guys,
I have a question..
I have an unlocked Ativ S with full file access.
Now iam searching for an installed XAP on my Device.
For my knowledge the xaps are encrypted and after installing them from the marketplace they are decrypted.
And what i want to know where can i find them on my phone?
especially iam searching for the gopro app which is a free app but doesn't work with the new gopro 4 version.
So i hope i can find a way to fix that with the xap.
But thats only possible if i can open the xap with a zip tool.
Hope you guys can help me and understand what i mean.
thx
The decompressed xaps are stored under D:\Data\Programs\ You'll see many GUIDS which coincide with the APP GUID. If you search for the app on windowsphone.com, you'll be able to see the app guid in the url segment.
You can't get the decrypted xap.
But you can repack the unencrypted .xap by zipping the collection of installed content as a same.
"C:\Data\Programs" (for WP8.0 Apps)
"C:\Data\Programs\WindowsApps (for WP8.1 Apps)
snickler said:
The decompressed xaps are stored under D:\Data\Programs\ You'll see many GUIDS which coincide with the APP GUID. If you search for the app on windowsphone.com, you'll be able to see the app guid in the url segment.
Click to expand...
Click to collapse
Under that string, there are only a few Cached pics:
Computer\Samsung ATIV S\Phone\Data\programs\{BCA90C60-10C7-4009-B8B0-13DF4EBCF9DA}
You may not be using full filesystem access, just the low-privilege version that you get if MtpSvc runs from C:\ but not as LOCALSYSTEM. Assuming you're capability-unlocked, you can use the AllCapabilities version of my webserver to access the install folders of each app.
Note that the actual "\Data\Programs\" folder is not readable by the webserver, but if you know the subfolder you want (such as an app's GUID) you can use that to browse and it works fine.
Note also that the apps are installed in a subfolder (called Install) of the GUID folder. So for example, the install directory for the GoPro app is
Code:
\Data\programs\{BCA90C60-10C7-4009-B8B0-13DF4EBCF9DA}\Install
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.
I remember when @djamol released the "root tool" app to the Windows store, which requires you to install it on SD Card, then to use the registry editor, you actually need to replace the files inside the XAP, which is quite genius
Anyways, I was thinking if the same trick done on root tool can be done on the old version of Extras + Info app too before Microsoft decides to remove its ability to move it to SD Card...
Modifying the WMAppManifest.xml inside the old XAP (removing anything related to interopservices to avoid throwing Error 0x81030120), set storage sense to SD Card, deploy app with App Deployment 8.1, then after deploying it, manually replace the modified XML file with the original untouched one (yes, the one with ID_CAP_INTEROPSERVICES and such) on SD Card with a PC (needs to unlock WPSystem folder first, we already did this in the past... ) open the app and see if Extras + Info still works and if yes, BOOTSTRAP vcReg and Interop unlock your device right away!
This might actually work! Someone should try this!
@djamol @vcfan @WojtasXda please take a look at this and see if it might actually work . We might be able to Interop Unlock WP8.1 again even after that Extras + Info app update lol XD
Sent from Ponyville
mrchezco1995 said:
I remember when @djamol released the "root tool" app to the Windows store, which requires you to install it on SD Card, then to use the registry editor, you actually need to replace the files inside the XAP, which is quite genius
Anyways, I was thinking if the same trick done on root tool can be done on the old version of Extras + Info app too before Microsoft decides to remove its ability to move it to SD Card...
Modifying the WMAppManifest.xml inside the old XAP (removing anything related to interopservices to avoid throwing Error 0x81030120), set storage sense to SD Card, deploy app with App Deployment 8.1, then after deploying it, manually replace the modified XML file with the original untouched one (yes, the one with ID_CAP_INTEROPSERVICES and such) on SD Card with a PC (needs to unlock WPSystem folder first, we already did this in the past... ) open the app and see if Extras + Info still works and if yes, BOOTSTRAP vcReg and Interop unlock your device right away!
This might actually work! Someone should try this!
@djamol @vcfan @WojtasXda please take a look at this and see if it might actually work . We might be able to Interop Unlock WP8.1 again even after that Extras + Info app update lol XD
Sent from Ponyville
Click to expand...
Click to collapse
I didn't really get your idea completely but as far as I get you want to modify WMAppMainfest.xaml file .
I have an application to edit any App Manifest but it doesn't work . you can't gain new capabilities to applications .
ngame said:
I didn't really get your idea completely but as far as I get you want to modify WMAppMainfest.xaml file .
I have an application to edit any App Manifest but it doesn't work . you can't gain new capabilities to applications .
Click to expand...
Click to collapse
Here's what I mean...
1. Modify the old Extras + Info app's WMAppManifest.xml file, removing every capability that requires Interop unlock first before actually sideloading the app.
2. Sideload the app to Lumia, with storage sense set it to SD Card.
3 . After sideload, check if Extras + Info app is installed on Settings but don't open it just yet.
4. Remove SD Card, insert it to PC, access WPSystem folder and find where the Extras + Info app is installed...
5. Once found, swap the modified WMAppManifest.xml file with the original unmodified one (yes, the one that had ID_CAP_INTEROPSERVICES and any capabilities OEM can only achieve)
6. Return SD Card to phone, and see if Extras + Info app opens... If it does open, Bootstrap vcReg.
7. After bootstrap, open Extras + Info and see if vcReg does run
Sent from Ponyville
mrchezco1995 said:
I remember when @djamol released the "root tool" app to the Windows store, which requires you to install it on SD Card, then to use the registry editor, you actually need to replace the files inside the XAP, which is quite genius
Anyways, I was thinking if the same trick done on root tool can be done on the old version of Extras + Info app too before Microsoft decides to remove its ability to move it to SD Card...
Modifying the WMAppManifest.xml inside the old XAP (removing anything related to interopservices to avoid throwing Error 0x81030120), set storage sense to SD Card, deploy app with App Deployment 8.1, then after deploying it, manually replace the modified XML file with the original untouched one (yes, the one with ID_CAP_INTEROPSERVICES and such) on SD Card with a PC (needs to unlock WPSystem folder first, we already did this in the past... ) open the app and see if Extras + Info still works and if yes, BOOTSTRAP vcReg and Interop unlock your device right away!
This might actually work! Someone should try this!
@djamol @vcfan @WojtasXda please take a look at this and see if it might actually work . We might be able to Interop Unlock WP8.1 again even after that Extras + Info app update lol XD
Sent from Ponyville
Click to expand...
Click to collapse
I've suggested this idea more than a year ago, but I heard from GDTD that it doesn't work as the WMAppManifest capabilities are only checked on deployment. Changing it after deployment would not work. Which is why they use the Preview for Developers app. It already has Interop capabilities and changing the manifest afterwards would not work, so they change the contents of the app instead, as this way any interop functions would work.
This is the current method now. You install an Interop app from the store and change the content.
AlvinPhilemon said:
I've suggested this idea more than a year ago, but I heard from GDTD that it doesn't work as the WMAppManifest capabilities are only checked on deployment. Changing it after deployment would not work. Which is why they use the Preview for Developers app. It already has Interop capabilities and changing the manifest afterwards would not work, so they change the contents of the app instead, as this way any interop functions would work.
This is the current method now. You install an Interop app from the store and change the content.
Click to expand...
Click to collapse
You know the root tool app released on store by @djamol ? The original WMAppManifest doesn't have any capabilities that enables it to read and write to the registry but after swapping the WMAppManifest file with the one that had interop capabilities, the app now works as what its intended.....
Sent from Ponyville
Try with OEM HTC Apps from store
mrchezco1995 said:
You know the root tool app released on store by @djamol ? The original WMAppManifest doesn't have any capabilities that enables it to read and write to the registry but after swapping the WMAppManifest file with the one that had interop capabilities, the app now works as what its intended.....
Click to expand...
Click to collapse
trick works for store apps, but it doesn't work with third party apps(sideloaded apps) because third party app can't use interopservices capability.
vcfan said:
trick works for store apps, but it doesn't work with third party apps(sideloaded apps) because third party app can't use interopservices capability.
Click to expand...
Click to collapse
so no luck for sideloaded OEM apps? That's sad
Sent from Ponyville
del......
WojtasXda said:
del......
Click to expand...
Click to collapse
What happened ?? Why you deleted your post ??
Have you stopped on working for new interop unlock method for wp8.1 that you tell us few days back ??
Is there any problem ??
Hello Guys is anybody please here to solve the problem of wp 8.1 interop unlock please we need it..?
I think Microsoft not allowing download Extra & Info to SD Card...thats the issue
_But but but....mixradio......
augustinionut said:
_But but but....mixradio......
Click to expand...
Click to collapse
What do you mean MixRadio?
vartanarsen said:
What do you mean MixRadio?
Click to expand...
Click to collapse
I mean this: http://forum.xda-developers.com/showpost.php?p=64118288&postcount=281
mrchezco1995 said:
Here's what I mean...
1. Modify the old Extras + Info app's WMAppManifest.xml file, removing every capability that requires Interop unlock first before actually sideloading the app.
2. Sideload the app to Lumia, with storage sense set it to SD Card.
3 . After sideload, check if Extras + Info app is installed on Settings but don't open it just yet.
4. Remove SD Card, insert it to PC, access WPSystem folder and find where the Extras + Info app is installed...
5. Once found, swap the modified WMAppManifest.xml file with the original unmodified one (yes, the one that had ID_CAP_INTEROPSERVICES and any capabilities OEM can only achieve)
6. Return SD Card to phone, and see if Extras + Info app opens... If it does open, Bootstrap vcReg.
7. After bootstrap, open Extras + Info and see if vcReg does run
Sent from Ponyville
Click to expand...
Click to collapse
actually the WMManifest.xml file is encoded with some kind of encoding so i don't think it's possible
i'm new to this forum please respond if i am wrong to say this
ngame said:
I didn't really get your idea completely but as far as I get you want to modify WMAppMainfest.xaml file .
I have an application to edit any App Manifest but it doesn't work . you can't gain new capabilities to applications .
Click to expand...
Click to collapse
try this
http://forum.xda-developers.com/win...erop-unlock-oem-unlock-windows-phone-t3467191
---------- Post added at 07:26 AM ---------- Previous post was at 07:25 AM ----------
Ranjan kataria said:
Hello Guys is anybody please here to solve the problem of wp 8.1 interop unlock please we need it..?
Click to expand...
Click to collapse
try this
http://forum.xda-developers.com/win...erop-unlock-oem-unlock-windows-phone-t3467191
---------- Post added at 07:27 AM ---------- Previous post was at 07:26 AM ----------
try this people....
http://forum.xda-developers.com/win...erop-unlock-oem-unlock-windows-phone-t3467191