Related
hey guys...i didnt find any other report about chevron's crashes...
i dont understand why!
all procedure is done...zune sdk tools and so on...when i start chevron and flag the 2 options instantly when press "unlock" the program crash...
i tryed to use all compatibility options and im admin on this account...im getting bored about this ehhehehe
Your pc's host file must NOT be read only. Chevron writes to it temporarily during the unlock. It will crash every time you click unlock if it is.
windows/system32/drivers/etc/hosts
I had the same Problem on my Windows 7 Notebook. Though I am admin on the NB, I found I had to run the Program as Administrator for it to work. It seems that the Program doesn't like UAC....
my host file is not Read Only...any other idea? i dont know maybe some particular driver for phone or something else
Virus? Malware?
Scan your pc first.
Disable antivirus, antimalware (live protections like TEA TIMER (spybot s&d))...
xardus said:
hey guys...i didnt find any other report about chevron's crashes...
i dont understand why!
all procedure is done...zune sdk tools and so on...when i start chevron and flag the 2 options instantly when press "unlock" the program crash...
i tryed to use all compatibility options and im admin on this account...im getting bored about this ehhehehe
Click to expand...
Click to collapse
Try reinstalling Windows
Had same problem with Chevron, and I had set write permission to the hosts file, reformatted SDHC card (that was working fine) with SD Formatter tool, re-flashed WP7 fresh.. to no avail.. until I went into WP7 "settings" app > "about" > "reset your phone".
Once I did this, I had no problem connecting to Zune, and Chevron. There must be a flag that gets set by the reset activity... Hope this solves your problem too!
host rewritten
i have had no luck with any of the above suggesting, making sure the host was not set to read only did keep it from chevron from crashing but then the host file just gets rewritten again and unlocker wont communicate with phone
Hello,
Try this,,,
After pairing your device with zutune,
Start All the zutune services
(If you are using an AV with a firewall, you should allow ChevronW7 pass through.)
Run ChevronW7.exe after then.
That works for me.
My system is W7_64x and AVG
Jpso said:
Hello,
Try this,,,
After pairing your device with zutune,
Start All the zutune services
(If you are using an AV with a firewall, you should allow ChevronW7 pass through.)
Run ChevronW7.exe after then.
That works for me.
My system is W7_64x and AVG
Click to expand...
Click to collapse
no luck still cant reunlock
xardus said:
my host file is not Read Only...any other idea? i dont know maybe some particular driver for phone or something else
Click to expand...
Click to collapse
hi,
I also had the same problem, was the antivirus that did crash, it was enough to disable it, and unlock work fine
Hi Guys, I also had the same problem and this is how it worked for me.
Disable the VGA driver and then run zune and then the chevron program in Administrator mode. Hope that helps someone.... if it doesnt probably it can be a problem with your windows sys files or it can be antivirus or windows defender or other programs.....
Hi,
i am trying to figure out how skype is working on my lumia 920.
i read something about integration in telefon function and always on and multitasking but for some reason noone sees me online .
just when i have the app open and running in the foreground.. why is the app not running in the background?
-adrian- said:
Hi,
i am trying to figure out how skype is working on my lumia 920.
i read something about integration in telefon function and always on and multitasking but for some reason noone sees me online .
just when i have the app open and running in the foreground.. why is the app not running in the background?
Click to expand...
Click to collapse
Seems its a bug atm. However, if anyone messages you even though you appear offline, you will get the message. Same with calls.
Hey guys. Have a problem with Skype. Recent update makes Skype only to Microsoft Account Sign in but I`m using different Skype accounts and don`t wanna merge them. So Is there any way to sideload old version of Skype? Found 2.13.0.290 but can`t sideload it. Application Deployment says "XAP file is invalid." and WPV XAP Deployer 2.0.0 says "Cannot read that as ZipFile". Same with current version available in store.
I have Lumia 620 with Black update and free unlock (2 apps I think).
winphoneuser said:
Hey guys. Have a problem with Skype. Recent update makes Skype only to Microsoft Account Sign in but I`m using different Skype accounts and don`t wanna merge them. So Is there any way to sideload old version of Skype? Found 2.13.0.290 but can`t sideload it. Application Deployment says "XAP file is invalid." and WPV XAP Deployer 2.0.0 says "Cannot read that as ZipFile". Same with current version available in store.
I have Lumia 620 with Black update and free unlock (2 apps I think).
Click to expand...
Click to collapse
You can't sideload XAPs from the store. Just connect one of your Skype accounts to a Microsoft account and problem solved...
You guys sideloading YouTube, right? Because there was good app. I need to use an older version of Skype whose allows me to login with my Skype creditenals instead of Microsoft one. I have found and tried "unlocked" Skype xaps with versions of 0.2.0.0, 1.0.0.0, 1.1.0.0. The most older version closes immidately after start and newer ones crashing when the cyan background appears. IM+ allows me to login with Skype but I can`t make voice calls through it.
So I need any version of Skype from 2.15.0.154 and lower that works with Lumia Black/GDR3 update. Maybe @AlvinPhilemon can help... And for sure I need non-interop version.
My point was that XAPs from the store are encrypted and thus can't be sideloaded, as you can only sideload plain unencrypted XAPs. How AlvinPhilemon obtained the unencrypted YouTube XAP is beyond me, but AFAIK the store encryption hasn't been broken yet, which leaves only the possibility of using either the XAP after it was installed (because they get decrypted after download) or taking the pre-installed one from the ROM (because those are also unencrypted).
Why is signing in with a Microsoft account such a problem for you in the first place? You need it to use most of the phone anyway, and as you've already experienced, older versions tend to have problems, so you will hardly get anything to work. And even if you do, there's always a possibility that Skype login still won't work in case MS changed something on their side.
Sadly I have no success with that
When I`m tricking a response with Fiddler, there is a c00cee3b error. I also tried to replace updated xap file on my SD card to outdated when install button is available on the SD card menu into marketplace. There is a constanly error during setup after 3/4 of the installing bar.
On interop-unlocked phones, it is possible (with some hacks) to extract the files for an app and re-build the .XAP archive. That's how the older YouTube version was resurrected.
GoodDayToDie said:
On interop-unlocked phones, it is possible (with some hacks) to extract the files for an app and re-build the .XAP archive. That's how the older YouTube version was resurrected.
Click to expand...
Click to collapse
I know. But there is also a problem with Skype xaps. Versions 0.2.0.0, 1.0.0.0 and 1.1.0.0 that I found unlocked are not working. v0.2.0.0 crashes immidately and newer ones shows cyan background before crash. There is also version 1.3.0.0 that have ID_CAP_INTEROPSERVICES string. Actual version 2.0.16.266 was "cracked" too and it also has that string.
I can`t install 1.3.0.0 and 2.0.16.266 versions on my Lumia 620 due to INTEROPSERVICES restriction and I can install 1.3.0.0 when ID_CAP_INTEROPSERVICES string is removed but it fails to work. It also crashing after the cyan background appears. 2.0.16.266 still gave an error after no ID_CAP_INTEROPSERVICES string but there is no reason for sideloading it - it`s available on the Marketplace and lacks of Skype account signing in support (people report that they still using their Skype account if they has been logged in in previous versions).
Give me old version of skype xap file. I'll do decrypt it.
djamol said:
Give me old version of skype xap file. I'll do decrypt it.
Click to expand...
Click to collapse
Tried I way that @djamol send me in my PM (yes, I still hope to get an old xap working on my phone!)
If you can successful install a skype without Interop Capability, then you succeed !!!
Just follow my steps to add Interop capability again.
Move skype on the SD Card.
Remove SD Card from the phone.
Insert SD Card on PC through card reader.
Now go to an Installation directory of skype in WPSystem\Apps\{***}\Install
Delete the DRM Encrypted WMAppManifest.xml file.
Now put your decrypted.xml which is an enabled Interop Capability.
Click to expand...
Click to collapse
I was little skeptical because of WMAppManifest.xml file. An idea to replace it and get some good things was discussed long ago with FAIL.
But anyway I did tried his method. I had successfully replaced that file but just didn't get needed result. App still crashes after the blue background appears for a second or less. Then I tried to move an app back to internal memory and then weird thing happened. Looks like it was failed to transfer my app back with modded file and an operation stuck somewhere between. Skype has disappeared both from Internal and SD card apps list of the Data/Storage Control ("Контроль памяти" in Russian) and it`s icon on the regular app list (one with all apps listed, opens by start screen swipe) turns into grey with no logo on it. When I tried to start it there is loading... ("Загрузка..." in Russian) sign with dot animation appears. I has leaved it in that state for the whole night but nothing happens and the phone was even half-charged after it.
Finally I have found new xap "for Lumia 610" which is WP7 xap and successfully sideloaded it but it crashes after the blue background like the all I tried before. FAIL
you just cant replace files and hope for the best.
sometimes you can trick apps with changed icons but not with complete xml codepages.
WMAppManifest.xml is used at installation of the application, but not to start the application.
Does anyone have the vevo xap for sideloading? I don't want to lose the app when I change phones or do a factory reset :'(
sent from my denim licious orange nokia 930
Does it even still work? Sounded like they were dropping support for it, not merely de-listing the app.
Not that it would surprise me if it does; I never installed it in the first place so I can't check.
It still works
Everyone advises to just not uninstall it from your phone but what happens if I need to do a hard reset or when I buy my next device?Someone has to have an unsigned xap. I asked Rafael on twitter but because its such public forum he didn't respond but he sometimes drops xaps that are able to side load kong after they're gone
So does anyone have the vevo xap?
i have the xap
@GoodDayToDie if I email it to you can you crack it?
If it's pulled right off the phone, sure; that's a really simple change.
If it's pulled off the store (DRM encrypted) then no, that's an excruciatingly complex wall of nonsense.
ok here it is
GoodDayToDie said:
If it's pulled right off the phone, sure; that's a really simple change.
If it's pulled off the store (DRM encrypted) then no, that's an excruciatingly complex wall of nonsense.
Click to expand...
Click to collapse
@GoodDayToDie
I'm not sure if this is a pulled of the store xap , but here you go, if you or anyone else is able to save it, id be so greatful! id even paypal a donation!
Taking a peek now.
Peek where?
@thals1992 look where the store?
Oh taking a peek
Sorry it's 6am a little sleepy
Its the XAP from the store. Encrypted....
Fudge is there anyone out there with the app already installed?
Can anyone else patch the xap?
noelito said:
Can anyone else patch the xap?
Click to expand...
Click to collapse
the xap posted cant be patched.
only one from the phone can be patched.
does anyone else have the app on their phone?
If you have the app on you phone will you please patch it? I'll even donate!
ok the app is on my phone can i patch it? also i have an old patched xap too
@ceesheim @GoodDayToDie @thals1992
ok I have the app on 2 of my phones an HTC 8X and a nokia 930, I read a tutorial to patch an xap but you need a phone with an sd card, is that the way to get the app off my phone, but neither have sd card slots, with that being said is there still a way to patch the app that's on these phones? I am also uploading an old wp7 version of the vevo app that I downloaded off of winphonhub, its patched and works fairly well with occasional error message, can this patched xap help you patch a more current one?
also id like to add I have 2 windows phones 635 and 830 with sd card slots, this may sound like a silly question, can I put the current marketplace xap onto the sd card and patch it from within the phone? or does it need to be installed on the phone too as well? (which unfortunately they are not installed on my sd card slot phones)
noelito said:
@ceesheim @GoodDayToDie @thals1992
ok I have the app on 2 of my phones an HTC 8X and a nokia 930, I read a tutorial to patch an xap but you need a phone with an sd card, is that the way to get the app off my phone, but neither have sd card slots, with that being said is there still a way to patch the app that's on these phones? I am also uploading an old wp7 version of the vevo app that I downloaded off of winphonhub, its patched and works fairly well with occasional error message, can this patched xap help you patch a more current one?
also id like to add I have 2 windows phones 635 and 830 with sd card slots, this may sound like a silly question, can I put the current marketplace xap onto the sd card and patch it from within the phone? or does it need to be installed on the phone too as well? (which unfortunately they are not installed on my sd card slot phones)
Click to expand...
Click to collapse
it MUST be installed on a phone with an sd card so that you can move the app to the sd card, then you can get the app of the phone and patch it.
if it isn't installed on your 830 then the xap only will not help you because the market place checks if the app is there , if it isn't then it will not let you install the the app
there are some hardcore ways to get the app of your x8 but that is only for real advanced users like @compu829 , because you need to actually brick your phone to enable mass storage mode . there are some threads about that.
@noelito if you upgrade your L930 to Windows Phone 10, there is a simple way for you to get the xap off of the device for backup!
i can definitely upgrade the L930 to w10 tp
@compu829 ok how to back up the xap? where is the tutorial? I am looking for the way to upgrade non supported devcies to windows 10 phones, I should be good to go because I have noupgrade the windows insider app
is this the link? and when do i do the back up / extract?
ok I found this thread @compu829
http://forum.xda-developers.com/windows-10/general/howto-install-windows-10-phones-t3030105
do I follow the instructions on this thread to install windows 10 on my 930?
however at what point am I able to extract the vevo app and patch, when do I do that?
I was thinking about having you update your phone and then using the following trick to access c:\ on the phone: http://forum.xda-developers.com/win...ranted-c-access-windows-10-technical-t3032766 I know that your model is supported in the next version of the preview when it is released.
@compu829 yes I read the Lumia icon will be supported for windows 10 tp but they didn't mention 930 could have been inadvertently left out, I think I have done this before, if you are able to give step by step instructions im even open to doing a remote access to my PC if you wanted to do it for me or guide me as I go a long doing it
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 recently bought a treasure tag and had to see that the WP app is no longer published, meaning this useful piece of plastic is not usable for me right now. I was able to find the original app as .XAP and .APPX-BUNDLE but since that app was once published, it is now encrypted and can't be sideloaded without getting error messages.
Is there any way to get the app working again? I basically need a XAP deployment tool which is able to "pirate" these extensions so that I can use my treausre tag finally.
Is there any tool out there or did one of you maybe made a homebrew version of that app ?
is possible if you have patched version of app...
talked about this here: http://forum.xda-developers.com/windows-phone-8/help/qa-photosynth-microsoft-store-t3182245
but Treasure Tag app is still in Store... maybe you not look carefully
install SysApp Pusher and under Microsoft Mobile - Tools, is Treasure Tag app...
dxdy said:
but Treasure Tag app is still in Store... maybe you not look carefully
install SysApp Pusher and under Microsoft Mobile - Tools, is Treasure Tag app...
Click to expand...
Click to collapse
Strange Thing whenever I searched for it manually I never got a result, using links to the store page only displayed N/A so not avialable using sysapp pusher I was able to press download but I get the error same error Code like other removed previously Nokia System apps get. ( error: 0x803F8001)
I'm on WM10 build 10512
then problem is in Win 10... work fine on 8.1...
just checked... install is appx format, not XAP...
you can download it direct from store, is not DRM protected
download link
dxdy said:
then problem is in Win 10... work fine on 8.1...
just checked... install is appx format, not XAP...
you can download it direct from store, is not DRM protected
download link
Click to expand...
Click to collapse
Hmm still "there is a Problem" Message Options are 'uninstalling' and 'buy'
Taping buy of Course does nothing, maybe it's because Nokias Device Hub app is missing?
try deploy APPX from computer to phone with deployer tool from SDK
dxdy said:
try deploy APPX from computer to phone with deployer tool from SDK
Click to expand...
Click to collapse
Only error codes.
I tried getting an shortcut from the removed Device Hub app and it was successfully, but launching Treasure Tag from the was not greated with any success, I guess it's for whatever reason not deployable on WM10 yet.
I may roll back to 8.1 GDR3, install treasure tag and upgrade to WM10 again, maybe this will work