Could someone to develop INTERNAL xap installer program [ homebrew] that
will be able to install xap inside phone ?
Thanks.
the os already has its own framework for that so no point, the installation of non signed apps is discussed loads on the forum. An app is avail called chevron to achieve it, unless you have updated your phone it should still work
I have investigated this. No luck so far. But I have a couple of leads that may let me make it. But it needs more research. I will have a look at it soon. But I can't give an ETA. So far I know there are no others that have succeeded so far.
Ciao,
Heathcliff74
This will be key for cydia/installius kind apps for WP7
anarchyuk said:
the os already has its own framework for that so no point, the installation of non signed apps is discussed loads on the forum. An app is avail called chevron to achieve it, unless you have updated your phone it should still work
Click to expand...
Click to collapse
is it possible ? I like to install apps inside the phone as in WINMO.
I can have XAP on skydrive a if i click it on browser it will automatically download and install, this will be awsome.
marek1 said:
is it possible ? I like to install apps inside the phone as in WINMO.
I can have XAP on skydrive a if i click it on browser it will automatically download and install, this will be awsome.
Click to expand...
Click to collapse
Nope. Not possible. Read my previous answer. Anarchyuk did not understand your question correctly.
Sent from my OMNIA7 using XDA Windows Phone 7 App
Heathcliff74 said:
Nope. Not possible. Read my previous answer. Anarchyuk did not understand your question correctly.
Sent from my OMNIA7 using XDA Windows Phone 7 App
Click to expand...
Click to collapse
Why is not possible, reason ? Will Mango make it possible ?
marek1 said:
Why is not possible, reason ? Will Mango make it possible ?
Click to expand...
Click to collapse
No. Microsoft doesn't want you to sideload apps. They want you to use the Marketplace. If you would be able to use an internal xap installer, you would be using it for sideloading.
It is not possible to use the API's for installing XAP's because you need TCB access for that. Normal apps have only LPC access, so normally you can't create an app for that. Needs hacking.
Ciao,
Heathcliff74
Would this type of access be possible with the 'DLLImport Project'?
So today i installed a random app from marketplace to see what was going on i the process-list. Here i saw "PacmanInstaller.exe" (after "Downloading..." > "Installing..."); later i tried to remote execute that one without any important args, and it said "This application can not run in Win32 mode.", eh? Didn't that exe just ran in the process list. Seems weird not to be able to launch that one. (it did not say the exe did not exist).
Tested another thing to, what happens when i deploy an app from Visual Studio??
>PacmanInstaller.exe shows up there too.?!?!?
THEN WTF, WHERE IS THE DRM?
Found this in "PacmanInstaller.c":
if ( v19 != v2 )
*(_DWORD *)(v17 + 4 * v18 - 4) = L"ID_CAP_DEBUG";
XAP > Phone side:
- IO Explorer, all files have the exact same byte size, no magic changes added "ID_CAP_DEBUG""
- No "WMAppPRHeader.xml" added (generated/downloaded)
__
This means its just copying it to phone (XAP).
Runs pacman to register app > \Applications\Install\GUID\Install
"PacmanInstaller.exe GUID" ??
>Cant execute remote PacmanInstaller? From within?
Just having fun, thanks
SimzzDev said:
Would this type of access be possible with the 'DLLImport Project'?
Click to expand...
Click to collapse
Nope. DllImport project is about accessing native API's. Not really about elevating privileges (so far). The package manager API's are native API's, but they require elevated privileges too. For having higher privileges you need to hack the system...
fiinix said:
So today i installed a random app from marketplace to see what was going on i the process-list. Here i saw "PacmanInstaller.exe" (after "Downloading..." > "Installing..."); later i tried to remote execute that one without any important args, and it said "This application can not run in Win32 mode.", eh? Didn't that exe just ran in the process list. Seems weird not to be able to launch that one. (it did not say the exe did not exist).
Click to expand...
Click to collapse
"This application can not run in Win32 mode" is error 0xbf:
Error 0xbf: error_invalid_exe_signature
Description: Cannot run <application> in Windows NT mode
Or: Cannot run <application> in Win32 mode
This means that your executable is not properly signed / elevated to launch into the required account.
fiinix said:
This means its just copying it to phone (XAP).
Runs pacman to register app > \Applications\Install\GUID\Install
"PacmanInstaller.exe GUID" ??
>Cant execute remote PacmanInstaller? From within?
Just having fun, thanks
Click to expand...
Click to collapse
C'mon fiinix! You of all people should know!!
Code:
<!-- Rule loaded from: \IMGFS\969eb155-55ff-4884-9ecb-241c8a4b6e09.policy.xml(405,6) -->
<Rule PriorityCategoryId="PRIORITY_STANDARD" ResourceIri="/LOADERVERIFIER/ACCOUNT/(+)/ACCOUNT_CAN_LAUNCH/NONE/NONE/PRIMARY/WINDOWS/PACMANINSTALLER.EXE" SpeakerAccountId="S-1-5-112-0-0-1" Description="Only TCB can launch into this chamber">
<!-- Authorize loaded from: \IMGFS\969eb155-55ff-4884-9ecb-241c8a4b6e09.policy.xml(406,10) -->
<Authorize>
<!-- Match loaded from: \IMGFS\969eb155-55ff-4884-9ecb-241c8a4b6e09.policy.xml(407,14) -->
<Match AccountId="S-1-5-112-0-0-1" AuthorizationIds="LV_ACCESS_EXECUTE" />
</Authorize>
<!-- Stop loaded from: \IMGFS\969eb155-55ff-4884-9ecb-241c8a4b6e09.policy.xml(409,10) -->
<Stop>
<!-- Match loaded from: \IMGFS\969eb155-55ff-4884-9ecb-241c8a4b6e09.policy.xml(410,14) -->
<Match AccountId="S-1-5-112-0-0XFF" />
</Stop>
</Rule>
That's why you can't run it! So, not the right account to launch. Not even when you use the Samsung exploit. Because that uses "Elevated". Not "TCB".
The proper way to call PacmanInstaller.exe is:
Code:
pacmaninstaller.exe <int> <guid>
I'm not really sure, but the <int> is the type of operation. Possible values are between 1 and 7 if I recall correctly. The guid is the applicationid. So far I know, the PacmanInstaller looks in \Application Data\Phone Tools\10.0\Install. That is where the xap's are initially uploaded to the phone and extracted by the packagemanger.
Ciao,
Heathcliff74
PS. New version of WP7 Root Tools coming up....
"Not even when you use the Samsung exploit. Because that uses "Elevated". Not "TCB"."
> What about "\Windows\Startup\"
That one launch what ever lnk (exe pointer) listed under startup directory. Would be an opportunity to restart after installed all "cydia" apps on the phone.
Another small but interesting find:
>Checking the mail launches another "servicesd.exe".
All those exe's of multiple sessions like "udevice.exe" and "servicesd.exe" go with an arg, right? then what is put in? Maybe an dll as arg?
>Then again, the custom dll (VS2008 made) will not run due it does not have "LV_ACCESS_EXECUTE", so that locks TCB out for dll arg inject.
udevice.exe (Driver host, runs under "SYSTEM" level)
servicesd.exe (Ordinary exe for dll host)
So making custom drivers wont work... (probably),
to be middle hand for executing under SYSTEM.
edit:
haha post "404" (current post count)
>HTTP Not Found.
Heathcliff74 said:
No. Microsoft doesn't want you to sideload apps. They want you to use the Marketplace. If you would be able to use an internal xap installer, you would be using it for sideloading.
It is not possible to use the API's for installing XAP's because you need TCB access for that. Normal apps have only LPC access, so normally you can't create an app for that. Needs hacking.
Ciao,
Heathcliff74
Click to expand...
Click to collapse
OK,I know that MS don't want to allow but I want to to know if is possible to hack it and do the internal XAP installer ? That's why I am asking.
I think that everybody who have unlocked phone will appreciate it !!
As everyone already said.. CANNOT be done. There's no, "I want to know if someone can hack this". The people working to bring full file/registry access and a better experience to all phones are too busy to worry about trying to make an internal xap installer. Just hook the damn thing up to a computer and use the applications to push a xap to your phone and be happy. I'm no admin or anything, but please don't pester over something like this.
Related
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.
[Q&A] [XAP][23/12/2014][0.4] CustomWPSystem - patch XAPs easily within WPSystem fold
Q&A for [XAP][23/12/2014][0.4] CustomWPSystem - patch XAPs easily within WPSystem folder
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [XAP][23/12/2014][0.4] CustomWPSystem - patch XAPs easily within WPSystem folder. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Help
Hi can u tell me step by step. What am i must do to patch this pfd? Thanks
Live Lock Screen beta
Hello! thanks for your work! I tried your CustomPFD xap and it works fine on my Lumia 620.
I'd like to try also the Live Lock Screen beta but I can not find the patched xap file to install with the CustomPFD.
Sorry for my english, can you help me to find the xap Live Lock Screen beta?
Many thanks!
@jackcicci ehm... I don't understand... Live Lock Screen beta is available within the store
Still getting errors, 3 different ones now at this point. Once I replicate the problem again I'll let you know what they were, one was access denied and the other was "App is not installed on SD Card or is unavailable," the third I'm trying to bring back up again (for now I'm getting the second error)
Swagulous said:
Still getting errors, 3 different ones now at this point. Once I replicate the problem again I'll let you know what they were, one was access denied and the other was "App is not installed on SD Card or is unavailable," the third I'm trying to bring back up again (for now I'm getting the second error)
Click to expand...
Click to collapse
Hi, you will help CustomWPSystem version 5
Pasquiindustry said:
@jackcicci ehm... I don't understand... Live Lock Screen beta is available within the store
Click to expand...
Click to collapse
Thanks, maybe I'm wrong, I was following this guide http://forum.xda-developers.com/win...p-customwpsystem-patch-xaps-wpsystem-t2975419
Choose the app target
With this first version it's possible to choose only three target apps, i will add other apps soon:
Live Lock Screen beta
Glance Background beta
Preview for developers
Field Medic
Download the app and move it to SD card (using storage sense)
Choose the custom XAP (the app uses the integrated file picker)
Patch!
I found the custom xap of Preview for developers and also Glance Background beta but i can't find the custom xap of Live Lock Screen beta and Field Medic.
Question
You can replace the bootscreen with this.
But witch one?
The one with the windows Logo or the "Nokia" ?
And how to put it in correct folder "c/user/etc etc " ?
Never mind, just found out
I tried all 4 apps, but only preview for developers works?
Galance Background beta crashs after patch, the other two cannot be patched.
Pasquiindustry said:
@jackcicci ehm... I don't understand... Live Lock Screen beta is available within the store
Click to expand...
Click to collapse
jackcicci said:
Thanks, maybe I'm wrong, I was following this guide http://forum.xda-developers.com/win...p-customwpsystem-patch-xaps-wpsystem-t2975419
Choose the app target
With this first version it's possible to choose only three target apps, i will add other apps soon:
Live Lock Screen beta
Glance Background beta
Preview for developers
Field Medic
Download the app and move it to SD card (using storage sense)
Choose the custom XAP (the app uses the integrated file picker)
Patch!
I found the custom xap of Preview for developers and also Glance Background beta but i can't find the custom xap of Live Lock Screen beta and Field Medic.
Click to expand...
Click to collapse
simonand said:
Galance Background beta crashs after patch, the other two cannot be patched.
Click to expand...
Click to collapse
I've still not understood where to find the modified xap of Live Lock Screen beta and Field Medic, I'm speaking about the custom XAP that has to be patched with the integrated file picker of the CustomWPSystem app after moving to the SD card the "orginal" app downloaded from the MS store as suggested by Pasquiindustry in the previous reply
Any ideas?
Error while swapping Live Lockscreen Beta
I tried to patch live lock screen beta with @-W_O_L_F-'s lock screen app. but I'm getting error "Cannot create a file when that file already exists. (Exception from HRESULT:0x800700B7)"
Please solve it and update ur xap
custom wpsystem manual swap will work to change firmware version in windows 10 .
---------- Post added at 06:55 AM ---------- Previous post was at 06:42 AM ----------
i need 'CustomWPSystem_0300.xap' the latest version not worked for me.when i tried its get back to app list
where is CustomPFD_0002.xap?
can't find CustomPFD_0002.xap file anywhere. CustomWPSystem still crashes when i apply CustomPFD_0003.xap
Can't grant access to SD card
I can't grant permission for the app to access SD card anymore since I updated to windows 10. Please fix it. Thanks you.
I'm sorry, I'm nt understanding how to install. Do I need a PC? If not, can you give me a detailed guide on how to do this? Thanks!
Yes, you definitely need a PC, same as you need for sideloading any homebrew. You need a Windows PC, a USB cable, and the Windows Phone SDK installed (this can be downloaded for free from MS, or is part of the more recent Visual Studio versions). Run "Windows Phone Developer Registration", enter you Microsoft Account info; that unlocks your phone for sideloading. Then run "Application Deployment" and select the XAP file, then hit Deploy; that installs the app.
This stuff is well documented, both on XDA and on other sites including MSDN. Please search before posting!
GoodDayToDie said:
Yes, you definitely need a PC, same as you need for sideloading any homebrew. You need a Windows PC, a USB cable, and the Windows Phone SDK installed (this can be downloaded for free from MS, or is part of the more recent Visual Studio versions). Run "Windows Phone Developer Registration", enter you Microsoft Account info; that unlocks your phone for sideloading. Then run "Application Deployment" and select the XAP file, then hit Deploy; that installs the app.
This stuff is well documented, both on XDA and on other sites including MSDN. Please search before posting!
Click to expand...
Click to collapse
I did search, and nothing came up for this! Anyway, thanks. How many GB is the SDK?
Don't remember exactly, but the web installer is tiny. https://www.visualstudio.com/en-us/downloads#d-express-windows-8, use the "Install Now" link to avoid downloading anything you don't need, then run the installer and just grab the WP8 parts.
Any way to install Lumia camera 5.0 on unsupported devices like 535 or 925
hey guys..is there any Any way to install Lumia camera 5.0 on unsupported devices like 535 or 925...???
please tell me ...sorry if i have posted it in wrong forum....
please reply me...
You could spoof the device ID (using an HTTPS proxy like Fiddler, or using a registry editor such as Root Tool if you have an SD card), and that should allow you to install the app. There's absolutely no guarantee it will work, though; it probably requires some per-device fancy hardware support. Worst case, it could actually screw up your phone's camery.
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.
So i upgraded my Huawei W1 to WP10 TP. Unfortunately I'm facing several problems:
1) I can't deploy .xap files anymore (I guess the backward compatibility ended with WP10)
2) The store won't let me download Here Drive (the device doesn't meet the requirements)
3) Being a smart cookie I tried downloading Here Drive from the store manually but I only get an .xap file which due to 1) I can't deploy to my device
So my questions are:
1) Is there a way how I still can deploy a .xap file to a WP10 phone?
2) Does the store use the registry to determine if a phone is capable of running an app? If so: If I edit the registry to fake a capable device, will I be able to install from store and run the app?
3) Can I force the store to provide the app in .appx rather than .xap file format? General procedure for manual downloading mentioned here http://forum.xda-developers.com/windows-phone-8/apps-games/apps-marketplace-t3171675
1) Have you tried openning developer mode?
2) Yes
3) What will it do if the app is an appx rather than xap?
@tolipwen
3) No appx is appx and xap is xap
mlleemiles said:
1) Have you tried openning developer mode?
2) Yes
3) What will it do if the app is an appx rather than xap?
Click to expand...
Click to collapse
My phone is in developer mode and I'm using (well trying to) WinAppDeployCmd. Unfortunately this will only accept .appx or .appxbundle. So the tool will just refuse sending an .xap to my phone running WP10.
On WP8.1 I used WPV XAP Deployer 2.0 for deploying my apps but it won't recognize my wp10 phone anymore. Is there an alternative that I'm missing?
mlleemiles said:
1) Have you tried openning developer mode?
2) Yes
3) What will it do if the app is an appx rather than xap?
Click to expand...
Click to collapse
titi66200 said:
@tolipwen
3) No appx is appx and xap is xap
Click to expand...
Click to collapse
Yes those are two different definitions. What puzzled me was that the store only offered me xap files for download and I tried like 50 apps. I thought most of them would be in the current .appx format.
EDIT: Solved. For some reason my phone gets recognized by the XAP deployer 2.0 now.
how can i update to wp10? I have problem with low storage....
qquiderr said:
how can i update to wp10? I have problem with low storage....
Click to expand...
Click to collapse
have a look at this:
http://forum.xda-developers.com/showpost.php?p=62138532&postcount=106
tolipwen said:
have a look at this:
http://forum.xda-developers.com/showpost.php?p=62138532&postcount=106
Click to expand...
Click to collapse
not work for me, im succes to removing languages, but if i factory rest, the phone stop working, still restarting... can you write here full tutorial in english step by step? (without russian videos).
qquiderr said:
not work for me, im succes to removing languages, but if i factory rest, the phone stop working, still restarting... can you write here full tutorial in english step by step? (without russian videos).
Click to expand...
Click to collapse
You're not supposed to factory reset your phone. In the post I quoted is a step-by-step guide in english. The russian videos are just to clear things up. Please reply in the quoted thread and state at which point you run into troubles.
tolipwen said:
You're not supposed to factory reset your phone. In the post I quoted is a step-by-step guide in english. The russian videos are just to clear things up. Please reply in the quoted thread and state at which point you run into troubles.
Click to expand...
Click to collapse
i delete english lang i now kept it and all works, i have win 10
How to update to 10.0.10586.29 (final)? I have previous version, but updating not working... its need to flash w 8.1 and do upgrade again?
tolipwen said:
So i upgraded my Huawei W1 to WP10 TP. Unfortunately I'm facing several problems:
1) I can't deploy .xap files anymore (I guess the backward compatibility ended with WP10)
2) The store won't let me download Here Drive (the device doesn't meet the requirements)
3) Being a smart cookie I tried downloading Here Drive from the store manually but I only get an .xap file which due to 1) I can't deploy to my device
So my questions are:
1) Is there a way how I still can deploy a .xap file to a WP10 phone?
2) Does the store use the registry to determine if a phone is capable of running an app? If so: If I edit the registry to fake a capable device, will I be able to install from store and run the app?
3) Can I force the store to provide the app in .appx rather than .xap file format? General procedure for manual downloading mentioned here http://forum.xda-developers.com/windows-phone-8/apps-games/apps-marketplace-t3171675
Click to expand...
Click to collapse
Obtained decrypted xap. (which will be regular marketplace signed)
Tap to Open > Install.
Very easy.
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