Related
Can do this using the Registry Viewer and Network Profile Tool. I will be making a tool for samsung that will allow you to provision any xml.
Sent from my OMNIA7 using Board Express
Awesome. Care to share how?
Indeed very good news. When do you think the tool will be ready ?
Okay here it goes, its very similar to the HTC method which requires alot of tinkering.
Firstly, you need to be Dev Unlocked. Search for Chevron Unlocker if you dont already have it.
Secondly, you will need Tom XAP Installer which can be found as a sticky at the top of the thread.
Lastly you will need nico's Registry Viewer XAP Package which can be found here: http://forum.xda-developers.com/showpost.php?p=10623201&postcount=19
Now when you have all the above done, Load up Registry Viewer and goto:
HKLM\System\State\Samsung\Phone\Operator\Base
You will see some numbered subkeys. You can edit any of these but I reccommend editing [1].
Now navigate to [1] and tap FileName this is where you enter the desired xml.
Now I have a UK Omnia 7 but I flashed the Unbranded XENJK1 ROM which is for Netherlands. So whenever you run the Network Profile App you will see the Network for the sim card you are currently using plus 4 other networks to choose from which will be Netherlands Phone Operators.
Here is a little example to run your desired provxml file. Remember we tapped on FileName in the [1] subkey, now clear the current filename thats already there and type in: UK_XEU_BASE.xml
Exit Registry Viewer and startup the Network Profile App and Tap on the Top Profile. (This is why we edited [1]). You will see the loading dots in the middle of the screen to tell you the device is busy (thats the provxml installing). When its done, exit the Network Profile App and restart it. You will now notice that ALL the UK network providers are now in the Profile list.
So this definately works, we just now need a way to create our own provxml files and copy them to the Windows folder on our Omnia 7!
So this in effect is the same as what I found/hit in this thread. The problem is, we don't have a way of writing to the \windows directory. I've tried all sorts of things to read the provxml from other locations but it doesn't want to.
RustyGrom said:
So this in effect is the same as what I found/hit in this thread. The problem is, we don't have a way of writing to the \windows directory. I've tried all sorts of things to read the provxml from other locations but it doesn't want to.
Click to expand...
Click to collapse
If what he described (anyone tested it with a custom provxml file yet?) works, then maybe the network profile app doesn't need a provxml file within the Windows folder (to test too).
Patch network setup dll to apply provxml from the xap install folder.
i 've do this on my htc provxml deployer by this way you can deploy custom provxml.
RustyGrom said:
So this in effect is the same as what I found/hit in this thread. The problem is, we don't have a way of writing to the \windows directory. I've tried all sorts of things to read the provxml from other locations but it doesn't want to.
Click to expand...
Click to collapse
Yes its more or less the same, also the method everyone is using for Interop to use native DLLs in their code is only for using Subs/Functions inside of Interfaces. Now to call an Exported Function in a native DLL requires a different approach. We first have to build a DLL using C++ in Visual Studio 2008 for Windows Mobile 6 (yes you heard me right! ) and create an interface for the functions we wish to use in the native DLL we want to call. We then use C# to use the ComBridge method to load the custom made native DLL which will then provide us the access to the Subs/Functions so when these are called, our custom made DLL will then call the Exported Function in our target DLL.
Now this will also enable us to use the Exported Functions in Coredll.dll which have all the juicy functions that we used and loved in Windows Mobile, including Registry read and write and file access and IO operations.
Now, Any C++ Volunteers???
martani said:
If what he described (anyone tested it with a custom provxml file yet?) works, then maybe the network profile app doesn't need a provxml file within the Windows folder (to test too).
Click to expand...
Click to collapse
It definately works with xml in windows folder but not tried a custom one yet.
lyriquidperfection said:
Now when you have all the above done, Load up Registry Viewer and goto:
HKLM\System\State\Samsung\Phone\Operator\Base
..........................
Click to expand...
Click to collapse
We can do the same by runnig "/windows/AppPreInstaller.exe path_to_provxml_file" (using l3v5y.WP7DT.RemoteExecute).
The problem is that AppPreInstaller.exe refuses any attempts to install provxml from any place outside /windows folder.
xboxmod said:
Patch network setup dll to apply provxml from the xap install folder.
i 've do this on my htc provxml deployer by this way you can deploy custom provxml.
Click to expand...
Click to collapse
But aren't the DLLs signed? Did you just resign it with a different cert?
lyriquidperfection said:
Yes its more or less the same, also the method everyone is using for Interop to use native DLLs in their code is only for using Subs/Functions inside of Interfaces. Now to call an Exported Function in a native DLL requires a different approach. We first have to build a DLL using C++ in Visual Studio 2008 for Windows Mobile 6 (yes you heard me right! ) and create an interface for the functions we wish to use in the native DLL we want to call. We then use C# to use the ComBridge method to load the custom made native DLL which will then provide us the access to the Subs/Functions so when these are called, our custom made DLL will then call the Exported Function in our target DLL.
Now this will also enable us to use the Exported Functions in Coredll.dll which have all the juicy functions that we used and loved in Windows Mobile, including Registry read and write and file access and IO operations.
Now, Any C++ Volunteers???
Click to expand...
Click to collapse
I know some people (davux) have started this. I wrote a simple one but I suck at C++ so didn't get very far.
lyriquidperfection said:
It definately works with xml in windows folder but not tried a custom one yet.
Click to expand...
Click to collapse
That reg key doesn't include a path, just a file name. I guess you could throw in DiagnosisApp_1.provxml and see if it launches it (it just installs the Diagnosis app).
denominator77 said:
We can do the same by runnig "/windows/AppPreInstaller.exe path_to_provxml_file" (using l3v5y.WP7DT.RemoteExecute).
The problem is that AppPreInstaller.exe refuses any attempts to install provxml from any place outside /windows folder.
Click to expand...
Click to collapse
yes and this apps doesn't deploy custom provxml!
i've try on my Htc by editing provxml called by this apps.
apppreinstaller is run on 1st boot to install in rom Xap's via a provxml.
RustyGrom said:
That reg key doesn't include a path, just a file name. I guess you could throw in DiagnosisApp_1.provxml and see if it launches it (it just installs the Diagnosis app).
Click to expand...
Click to collapse
Ha! I entered DiagnosisApp_1.provxml into the FileName value and when I applied the modified profile, it did indeed install the Diagnosis App but not launch it. The provxml is for installation only as when I did this, Diagnosis appeared in my app list without keying in ##634# in the dialer!
lyriquidperfection said:
Ha! I entered DiagnosisApp_1.provxml into the FileName value and when I applied the modified profile, it did indeed install the Diagnosis App but not launch it. The provxml is for installation only as when I did this, Diagnosis appeared in my app list without keying in ##634# in the dialer!
Click to expand...
Click to collapse
Cool so as best I can tell looking at the disassembled code SetNetworkSetting(string settingName, out int bRet) from NwProfDLL.dll does that with "settingName" being the provxml file or the name assigned to the provxml file, leaning towards the latter.
Edit... maybe not... doesn't seem to work to launch DiagnosisApp_1.provxml. Might be due to my phone being carrier locked?
RustyGrom said:
Cool so as best I can tell looking at the disassembled code SetNetworkSetting(string settingName, out int bRet) from NwProfDLL.dll does that with "settingName" being the provxml file or the name assigned to the provxml file, leaning towards the latter.
Edit... maybe not... doesn't seem to work to launch DiagnosisApp_1.provxml. Might be due to my phone being carrier locked?
Click to expand...
Click to collapse
I have the same problem, too. My OMNIA 7 is still carrier locked (bad bootloader version...). I will try to unlock it tomorrow.
Doesnt matter if it is locked or unlocked. It doesnt launch it only installs it. It adds the icon to the app list if it wasnt there already.
Sent from my OMNIA7 using Board Express
lyriquidperfection said:
Doesnt matter if it is locked or unlocked. It doesnt launch it only installs it. It adds the icon to the app list if it wasnt there already.
Sent from my OMNIA7 using Board Express
Click to expand...
Click to collapse
In the NetworkProfile app, I can't choose a profile. It just says "This application can not be used if the device is in network locked state by mobile operator."
I tried bypassing it and just calling the function from my own code but it didn't work. That doesn't mean it won't work as I may be doing something wrong but the COM DLL could be checking the phone's lock status before trying to run the provxml.
RustyGrom said:
In the NetworkProfile app, I can't choose a profile. It just says "This application can not be used if the device is in network locked state by mobile operator."
I tried bypassing it and just calling the function from my own code but it didn't work. That doesn't mean it won't work as I may be doing something wrong but the COM DLL could be checking the phone's lock status before trying to run the provxml.
Click to expand...
Click to collapse
I don't think it's so much if the device is carrier-locked, but if the device is carrier-branded. I couldn't use the Network Profile tool with my original T-Mobile UK ROM, but since flashing it with the generic ROM that leaked, I can now use it, despite still being carrier-locked.
guys on your samsung device operator xml are deployed by configxml.exe in the windows folder called by AutoSim.exe imself run by coldinit.exe
the operator provxml are named like this FRANCE_SFR_BASE.xml
i'm looking if i find somethink.
i think autosim is also run by NetworkProfile.
RustyGrom said:
In the NetworkProfile app, I can't choose a profile. It just says "This application can not be used if the device is in network locked state by mobile operator."
I tried bypassing it and just calling the function from my own code but it didn't work. That doesn't mean it won't work as I may be doing something wrong but the COM DLL could be checking the phone's lock status before trying to run the provxml.
Click to expand...
Click to collapse
I can confirm that it works on my carrier locked OMNIA 7 !.
I edited the filename in the registry, then I launched the Network profile app.
If the first profile is allready choosen on your device, choose the second one and then the first one. It works only for the [1] registry filename so you have to choose the first profile of the list.
After that the diagnosis app appears on your device...
Edit: my device is T-Mobile Germany branded...
INSTALLING HOMEBREW APPS
Ok, so I figured out how to get a homebrew app installed that has "INTEROPSERVICES".
NOTE: Most apps still don't load/work, but at least they can be installed. So, maybe someone can figure out what to do from here. In fact, the only app that works properly that I've tested is Navigator Select. Granted this app is probably signed with a cert or what ever because it's from an OEM.
Instructions;
1) Extract the XAP using 7Zip/WinRAR/etc.
2) Find WMAppManifest.xml & open it in an editor (Wordpad/Notepad/VS/Word/etc.).
3) Delete the line "<Capability Name="ID_CAP_INTEROPSERVICES"/>"
4) Save the file.
5) Compress all files from XAP into a ZIP
6) Rename ZIP to XAP
7) Install
RESUMIBLE APPS
Also, I found this article.
In order to make an app resumible, we'll edit the same file as above, but this tome we're going to add "ActivationPolicy="Resume"" to the "<DefaultTask Name="_default" NavigationPage="PivotPage.xaml" />" line so it looks like "<DefaultTask Name="_default" NavigationPage="PivotPage.xaml" ActivationPolicy="Resume"/>". Save file compress everything to ZIP & rename to XAP same as above. Now install apps using what ever side loader you like. I used "Tom XAP Installer".
NOTE: DON'T use the resumible hack on Navigator Select, at least on Mango. Otherwise it'll just show a black screen if you open it from the start menu/app list when you have a map open. You can still use task switcher to open it, but just not worth it. Than again this could be a Mango problem with the resume hack.
Anyone out there with a T-Mobile USA HD7 happen to have WPDM from Schaps installed & no Mango Beta? If so, can you see if you can copy out the TMOUS Cert that should be on your device. I'm on Mango, so cant. I want to try to sign a homebrew app with that cert & see if it'll work on Mango Beta.
I rolled back but have the HTC 7 Pro, so I can send you that cert, maybe you can edit it so it works with the HD7?
Glad to see you working on this btw .
blindpet said:
I rolled back but have the HTC 7 Pro, so I can send you that cert, maybe you can edit it so it works with the HD7?
Glad to see you working on this btw .
Click to expand...
Click to collapse
Thank you, it shouldn't matter which HTC device it comes from. The main issue is I'm on T-Mobile so for my device has T-Mobile's OEM cert on it where your 7 Pro most likely doesn't. Probably has a Verizon OEM or for what ever OEM you're on. Your device might have an HTC Cert though. The main thing I'm looking for is a cert that's trusted & allowed INTEROPSERVICES access as OEM's/Manufacturers are the only ones allowed this atm. This is why Navigon Select works even though it has INTEROPSERVICES. I'm hoping I can use the SDKCert Signer tool & an OEM cert to sign the dll's/mui's in the XAP with.
I'm on an unbranded HTC 7 Pro. If you walk me through extracting whatever certs you can use I'm more than happy to do it.
blindpet said:
I'm on an unbranded HTC 7 Pro. If you walk me through extracting whatever certs you can use I'm more than happy to do it.
Click to expand...
Click to collapse
Okay, you'll need WPDM. Install that to your pc/laptop. Once you run it the first time, it'll prompt to install TouchXperience. Open TouchXperience on your 7 Pro. Now WPDM will sync with it. Now open the file manager in WPDM on your PC. The certs should be in \windows or one of it's sub directories. I don't remember exactly where I saw them. Try to find one with HTC or Test in the file name. You can than copy if & paste it into windows explorer somewhere to zip it up & upload it here.
Unsigned app limit
Any idea which homebrew can get rid of the unsigned applications limit on Mango?
I am afraid of removing all my unsigned apps for nothing
Before following the OPs suggestions I was not able to deploy Navigon Select onto my device. After editing WMAppManifest.xml I was finally able to deploy it again. Sadly it won't work. After startup it tells me that it can't complete the registry process due to not being able to connect to the network. Pitty.
dkp1977 said:
Before following the OPs suggestions I was not able to deploy Navigon Select onto my device. After editing WMAppManifest.xml I was finally able to deploy it again. Sadly it won't work. After startup it tells me that it can't complete the registry process due to not being able to connect to the network. Pitty.
Click to expand...
Click to collapse
It worked for me, which version are you using. I have the patched 1.3 install with maps & everything.
Handala said:
Any idea which homebrew can get rid of the unsigned applications limit on Mango?
I am afraid of removing all my unsigned apps for nothing
Click to expand...
Click to collapse
Advanced Config has that feature. Not sure what else does. There's a couple apps that do it.
drkfngthdragnlrd said:
It worked for me, which version are you using. I have the patched 1.3 install with maps & everything.
Click to expand...
Click to collapse
Tried it with 3.0 and 1.4. Both patched. I wasn't able to deploy either one of them.
dkp1977 said:
Tried it with 3.0 and 1.4. Both patched. I wasn't able to deploy either one of them.
Click to expand...
Click to collapse
In order to deploy you have to edit that file I listed in the OP. I've got v1.3 installed as US maps only works with v1.3 & is what the map loader software came with.
EDIT: Whoops, v1.4 is what i have installed on Mango.
drkfngthdragnlrd said:
In order to deploy you have to edit that file I listed in the OP. I've got v1.3 installed as US maps only works with v1.3 & is what the map loader software came with.
EDIT: Whoops, v1.4 is what i have installed on Mango.
Click to expand...
Click to collapse
Yeah, I followed your advice and was able to deploy it successfully. But I just can't use it anymore since it won't registert. It keeps telling me to turn airplone mode off (which isn't on anyway).
dkp1977 said:
Yeah, I followed your advice and was able to deploy it successfully. But I just can't use it anymore since it won't registert. It keeps telling me to turn airplone mode off (which isn't on anyway).
Click to expand...
Click to collapse
Hum, no clue, I used Map Loader to add my maps. It turns my pc into the server. Have you checked you internet to make sure you have a good connection by loading any website in IE. Also, try WiFi. My only guess could be a data connection problem.
drkfngthdragnlrd said:
Hum, no clue, I used Map Loader to add my maps. It turns my pc into the server. Have you checked you internet to make sure you have a good connection by loading any website in IE. Also, try WiFi. My only guess could be a data connection problem.
Click to expand...
Click to collapse
Tried 3G and WiFi. No luck. -.-
dkp1977 said:
Tried 3G and WiFi. No luck. -.-
Click to expand...
Click to collapse
That sux, the server must not recognize a Mango device or something. My only suggestion is if you have iPhone Maps for Navigon Select, use Map Loader found here on XDA to load those maps.
drkfngthdragnlrd said:
Advanced Config has that feature. Not sure what else does. There's a couple apps that do it.
Click to expand...
Click to collapse
Ok thanks a lot, I'm going to try your trick then! Hope this homebrew will launch on Mango...
drkfngthdragnlrd said:
That sux, the server must not recognize a Mango device or something. My only suggestion is if you have iPhone Maps for Navigon Select, use Map Loader found here on XDA to load those maps.
Click to expand...
Click to collapse
k, I'll try. Gotta read the whole thread first, since it seems rather complicated to set up. Thanks for your help.
dkp are you dev unlocked?
WPDM is broken, it doesn't work with the new beta tools. I uninstalled them and reinstalled WPDM but it crashes on load. Unfortunately I don't have the time to mess with this now so if anyone else can provide the certs that'd be great.
Running touchxperience on my phone I can't find an HTC or Test folder in \windows.
blindpet said:
dkp are you dev unlocked?
WPDM is broken, it doesn't work with the new beta tools. I uninstalled them and reinstalled WPDM but it crashes on load. Unfortunately I don't have the time to mess with this now so if anyone else can provide the certs that'd be great.
Running touchxperience on my phone I can't find an HTC or Test folder in \windows.
Click to expand...
Click to collapse
No problem, I have the same problem with WPDM & the beta tools. I may just have to go back to NoDo to get them myself. At least now someone made a BAT files to update so hopefully I won't have to reset my HD7 to get back into Mango again.
Hi hackers,
Version 2.1 of DeployProvXML is here, and should be more robust than the previous version:
1: The CustClear.provxml file is now copied both using the filesystem DLL (like v1) and using XML provisioning (hopefully works aroudn the HTC update blocking filesystem access.
2: The CustClear.provxml file is now self-chaining. Really, this time - so long as you run the program *once*, you can even change the included CustClear.provxml, re-deploy, and run Connection Setup; your new version will then be copied to \Windows. (Re-run CS to actually process your new version). No more need to re-run DeployProvXML after each use of Connection Setup!
3. The program now contains more diagnostics. It sets a registry value at launch (using ComRegRW.DLL), changes that registry value (using provxml) when deploying the file, and changes it again when the deployed file is processed by Connection Setup (as part of the CustClear.provxml). It also checks that the value is as expected avter deploying.
REQUEST:
Anybody who has an interop-unlocked HTC phone with the latest official HTC update (meaning you can't use TouchXplorer anymore), please run this app, then run Connection Setup, then use a registry editor to check the key HKCU\Software\DeployProvXML. It should have a value, LastOperation. Please include the data in the value (or the fact that it doesn't exist) with your reports. Thank you!
Description:
Another handy little utility for people with HTC phones, this app simply copies a CustClear.provxml file from its install directory to \Windows, then exits. The idea is to make sure that you're never without at least a basic file that can be used by Connection Setup to unlock your phone. New in v2, every time you run Connection Setup, the file will automatically restore itself to the Windows directory. This ensures you'll never accidentally get caught with a locked phone after an upgrade or something!
The included Provxml has three parts. However, you can customize it however you like by opening the XAP file and editing the embedded provxml. The parts are:
1: Applies the registry settings to unlock the phone, including Interop-Unlock.
2: Applies a test value in the registry, at HKCU\Software\DeployProvXML. This value is harmless but can be used to test if the app is working.
3: Chain-copies itself from DeployProvXML's install folder into Windows again, replacing the copy that Connection Setup consumes.
Note that this program does not actaully apply the provxml, merely copies it to where Connection Setup expects to find it. It should close immediately after starting; this is not a bug. If you see a dialog box instead, something went wrong and you should report it below!
This program is only going to work on HTC phones, since it uses the HTC DLLs for provxml, file access, and registry. It is a 7.0 app but is compatible with Mango if you have Interop Unlock already.
XAP is in DeployProvxml\bin\debug. Source included for those interested.
Do you think a deployer for OMNIA 7 is possible ?
Maybe with a .dll of WP7 Root Tools ?
So users who didn´t prepare their device for our OnDevice provxml app under NoDo could also enable this feature...
contable said:
Do you think a deployer for OMNIA 7 is possible ?
Maybe with a .dll of WP7 Root Tools ?
So users who didn´t prepare their device for our OnDevice provxml app under NoDo could also enable this feature...
Click to expand...
Click to collapse
This has been solved I can finally test the app myself now. I changed the path to copy the provxml from the iso storage of the app instead of the provxml folder.
Interop.Services
Just read this http://translate.google.com/transla...oducing-windows-phone-7-5-native-programming/
Any joy?
Looks cool, but I'll need to investigate further. It has definitley been reproted that Homebrew apps without ID_CAP_INTEROPSERVICES don't work even in Mango. It sounds like this guy is maybe using a marketplace signed DLL, though? Not sure - the translation isn't great. He's working from an app that I've never explored, and that appears to be specific to the Japanese Mango phone.
how do we use it. will it permanently unlock when we update to official Mango?
Ttblondey said:
how do we use it. will it permanently unlock when we update to official Mango?
Click to expand...
Click to collapse
Install app in NoDo.
Run in once.
Upgrade to Mango.
Run the Connection Setup app (from Marketplace).
Hit "OK" in Connection Setup.
Your phone is now dev-unlocked and will not automatically relock. Additionally, you can now install Mango homebrew.
I suggest you then run DeployProXml again, since installing an update, even something like a HTC firmware update, may re-lock the phone. So long as you've run DeployProvXml since the last time you ran Connection Setup, though, you can unlock again.
If this helps, please hit Thanks!
piaqt said:
Just read this http://translate.google.com/transla...oducing-windows-phone-7-5-native-programming/
Any joy?
Click to expand...
Click to collapse
he does pretty much the same from what I read. You just use oem dll's and have some native functions to work with. f/e htc has file operations + regoperations + provxml, samsung has regoperations + provxml (trough which you can do regops). This manufacturer dll probably contains fileops as well, which is nice since there might also be a chance that there will be a working provxml method and with the fileops you can copy the provxml files to the desired location. In theory ofcourse.
Marvin_S said:
he does pretty much the same from what I read. You just use oem dll's and have some native functions to work with. f/e htc has file operations + regoperations + provxml, samsung has regoperations + provxml (trough which you can do regops). This manufacturer dll probably contains fileops as well, which is nice since there might also be a chance that there will be a working provxml method and with the fileops you can copy the provxml files to the desired location. In theory ofcourse.
Click to expand...
Click to collapse
There are two differences that are worth noting, though.
A) This is a phone that came with Mango. There was never any chance to unlock it for Mango homebrew. It blocks apps with ID_CAP_INTEROPSERVICES - something we had to work around with registry edits.
B) Related to A, he can call native code without having ID_CAP_INTEROPSERVICES. This isn't supposed to be possible at all. Makes me wonder if he's actually calling anything in the DLL or if he's just loading the COM object but not using it and calling that success.
GoodDayToDie said:
There are two differences that are worth noting, though.
A) This is a phone that came with Mango. There was never any chance to unlock it for Mango homebrew. It blocks apps with ID_CAP_INTEROPSERVICES - something we had to work around with registry edits.
B) Related to A, he can call native code without having ID_CAP_INTEROPSERVICES. This isn't supposed to be possible at all. Makes me wonder if he's actually calling anything in the DLL or if he's just loading the COM object but not using it and calling that success.
Click to expand...
Click to collapse
Ahh yeah your right. Yeah I realy wonder what the trick behind it is and if he manages to install it.
Something else I have not tried yet, but what happens if you deploy it without the id_cap and than run it. It will not work obviously, but what happens if you redeploy with the tag in? Will it still get rejected? Because the phone rejects the app I think.
Hey, the ZIP contains a folder, which, if I package into a XAP, fails on deployment. What's the best way to get this packaged into a usable XAP?
trying to figure out how to install this app.
@thesecondsfade:
Bottom line of the first post:
"XAP is in DeployProvxml\bin\debug. Source included for those interested."
I distribute most of my apps this way, unless the source is really big and the XAP alone is a significantly smaller download for some reason.
@Ttblondey:
Is your phone dev-unlocked?
Is your phone either pre-Mango, or interop-unlocked?
Do you have a XAP deployment program and the Zune software?
GoodDayToDie said:
@thesecondsfade:
Bottom line of the first post:
"XAP is in DeployProvxml\bin\debug. Source included for those interested."
I distribute most of my apps this way, unless the source is really big and the XAP alone is a significantly smaller download for some reason.
@Ttblondey:
Is your phone dev-unlocked?
Is your phone either pre-Mango, or interop-unlocked?
Do you have a XAP deployment program and the Zune software?
Click to expand...
Click to collapse
My TouchXplorer does not work anymore after updating to the official Mango, though my phone is still unlocked. This XAP will definitely helps if new firmware/updates come along to deploy Provxml to /windows.
I've installed it but how can I verify if this is being installed/copied to /windows?
GoingInside said:
My TouchXplorer does not work anymore after updating to the official Mango, though my phone is still unlocked. This XAP will definitely helps if new firmware/updates come along to deploy Provxml to /windows.
I've installed it but how can I verify if this is being installed/copied to /windows?
Click to expand...
Click to collapse
This app uses the same DLL as TouchXplorer, which means it doesn't work either (I wrote a number of apps using that DLL, including a backup tool, and none of them can see any files anymore). I'm not sure exactly what was changed, but yeah, they broke it. My hope is that Heathcliff74's WP7 Root Tools will restore file browsing on HTC soon.
As soon as I finish restoring my phone, I'll try writing a version of the app that uses ProvXML to copy the file, instead of ComFileRW.dll (which no longer works if you get the final HTC update). Using ProvXML is limited in some ways - you can't browse the filesystem, for example - but it works great for this type of operation.
i'm on force unlock from Ansar's thread with Pedbe way final mango.Been trying to use advancedconfig 1.3,1.4 battery meter it don't work anymore.Good thing I can sideload(that's important)
GoodDayToDie said:
This app uses the same DLL as TouchXplorer, which means it doesn't work either (I wrote a number of apps using that DLL, including a backup tool, and none of them can see any files anymore). I'm not sure exactly what was changed, but yeah, they broke it. My hope is that Heathcliff74's WP7 Root Tools will restore file browsing on HTC soon.
As soon as I finish restoring my phone, I'll try writing a version of the app that uses ProvXML to copy the file, instead of ComFileRW.dll (which no longer works if you get the final HTC update). Using ProvXML is limited in some ways - you can't browse the filesystem, for example - but it works great for this type of operation.
Click to expand...
Click to collapse
Ok, guess I'll have to wait for the experts (Heathcliff74 and you etc) to solve this HTC drive update issue. Thank you!
GoingInside said:
Ok, guess I'll have to wait for the experts (Heathcliff74 and you etc) to solve this HTC drive update issue. Thank you!
Click to expand...
Click to collapse
@GoingInside, and anybody else in the same boat (latest HTC update installed, filesystem browsing broken), please try the latest version (v2, now on the initial post)! After running the app once, run Connection Setup and hit OK. After you do that, use a Registry Editor to check for the presence of the following registry key: HKCU\Software\DeployProvXML.
Please report whether that key is present. If it is, that means the app is fully functional even with the latest update!
I only have a NoDo Backup (my phone came with nodo) - can I get the interop unlock trough dev unlocking the phone and then running our app?
nvm, I am now downgrading to NoDo and Will then update to the HTC RTM (the one that Comes via zune). As soon as I am there I will tell you if i had luck with it or not (I hope I can interopunlock on NoDo as the 3 apps sideloadlimit is crap)
Update 1: I am on NoDo and I started your app. It cloesd, i went to Connection Setup and ran it. Will check if the registry value is there as soon as some XAPs are deployed (first time that I can deploy more than 3 XAPs )
Update 2: Now going trough the Beta - RTM - HTC Update Update marathon. Will Report back as soon as I am on HTC's RTM
GoodDayToDie said:
@GoingInside, and anybody else in the same boat (latest HTC update installed, filesystem browsing broken), please try the latest version (v2, now on the initial post)! After running the app once, run Connection Setup and hit OK. After you do that, use a Registry Editor to check for the presence of the following registry key: HKCU\Software\DeployProvXML.
Please report whether that key is present. If it is, that means the app is fully functional even with the latest update!
Click to expand...
Click to collapse
Unfortunately, it seems that the new XAP (v2) doesn't work as well. Copy and deploy the latest DeployProvXML.xap (dated 5/10/2011) to my HTC trophy. After running Connection Setup, I can't find the registry key: HKCU\Software\DeployProvXML. I only found MICROSOFT under HKCU/Software/.
But please continue your research into this. THANKS!
In the past, Windows has had editions for consumers that did not include Remote Desktop enabled. Usually there was a patch to enable it. Recently it has been proved how there is almost no difference between Windows 8 and Windows RT and that RT is just a port of Windows 8. So what about all the system files? They can be changed just like x86 Windows. So what about enabling Remote Desktop, so we don't need a ARM remote app that we need to unlock Windows for, and we can use what comes with Windows. In the past we modified the termsrv.dll file and changed some registry settings. I've included the Windows 8 and the Windows RT versions of termsrv.dll so that maybe some clever ones might try and crack a solution to enabling it on Windows RT.
sionicion said:
In the past, Windows has had editions for consumers that did not include Remote Desktop enabled. Usually there was a patch to enable it. Recently it has been proved how there is almost no difference between Windows 8 and Windows RT and that RT is just a port of Windows 8. So what about all the system files? They can be changed just like x86 Windows. So what about enabling Remote Desktop, so we don't need a ARM remote app that we need to unlock Windows for, and we can use what comes with Windows. In the past we modified the termsrv.dll file and changed some registry settings. I've included the Windows 8 and the Windows RT versions of termsrv.dll so that maybe some clever ones might try and crack a solution to enabling it on Windows RT.
Click to expand...
Click to collapse
termsrv is a system service and how can we use a modified termsrv.dll before we use the Jailbreak tool?maybe we can edit termsrv.dll in the memory.
We can't, I suspect. Even after jailbreaking, the lack of a signature on a system file may be a problem. It's worth a shot, though.
termsrv.dll -should- be a usermode library that would be editable after the jailbreak.
I am able to take ownership of the file and replace it. But it won't use the termsrv.dll from my windows 8… I'm almost positive it is because the dll is different depending on architecture. But it should be as easily replaceable as any system file on windows 8, am I right? I don't see why it wouldn't but I could be wrong.
Yeah, pretty much. You definitely won't be able to use the Win8 version (x86 machine code, ARM processor, not gonna fly...) but a modified version of the Windows RT version might work. Bear in mind that since modifying the DLL will invalidate the signature, this won't work if the signature validation is enforced (i.e. you'll have to jailbreak).
Should be possible using the Remote Debugging Tools or, even better, cdb. Put it in a .cmd file in autorun and voila
clrokr said:
Should be possible using the Remote Debugging Tools or, even better, cdb. Put it in a .cmd file in autorun and voila
Click to expand...
Click to collapse
Please!! Remote desktop would be awesome enabled on the Surface RT, if someone could work on it I know a lot of people would be very grateful!
I've already posted a method that should enable RDP here: http://forum.xda-developers.com/showpost.php?p=36386089&postcount=211 - no need to patch DLL, and would work on an a locked device. But you'll have to manually edit binary registry value, instead of using a provided tool.
I have not tested RDP, but after using this method I was able to recover an option of joining device to Active Directory domain (it was blocked by the similar policies).
mamaich said:
I've already posted a method that should enable RDP here: http://forum.xda-developers.com/showpost.php?p=36386089&postcount=211 - no need to patch DLL, and would work on an a locked device. But you'll have to manually edit binary registry value, instead of using a provided tool.
I have not tested RDP, but after using this method I was able to recover an option of joining device to Active Directory domain (it was blocked by the similar policies).
Click to expand...
Click to collapse
Can you share how you managed to get the rt joined to a domain?
mamaich said:
I've already posted a method that should enable RDP here: http://forum.xda-developers.com/showpost.php?p=36386089&postcount=211 - no need to patch DLL, and would work on an a locked device. But you'll have to manually edit binary registry value, instead of using a provided tool.
I have not tested RDP, but after using this method I was able to recover an option of joining device to Active Directory domain (it was blocked by the similar policies).
Click to expand...
Click to collapse
Wouldn't both methods work though? Your method works by enabling features from other editions by telling Windows that's what edition it is running. It disables it when the Software Protection service restores it to the original template according to the edition. By patching the DLL file, you could trigger Remote Desktop to work without it needing to check in with the kernel policies.
I mean unless you have a way to modify these policies without all the extra occuring, it would work. But Bitlocker and the Software Protection service getting involved...it just sounds like a lot of extra work for something much bigger in the end, and I know there must be an easier way to force Remote Desktop to work without listening to these policies because it has been done in the past.
mamaich said:
I've already posted a method that should enable RDP here: http://forum.xda-developers.com/showpost.php?p=36386089&postcount=211 - no need to patch DLL, and would work on an a locked device. But you'll have to manually edit binary registry value, instead of using a provided tool.
I have not tested RDP, but after using this method I was able to recover an option of joining device to Active Directory domain (it was blocked by the similar policies).
Click to expand...
Click to collapse
I tried to enable one of the Remote Desktop vars last night, allowRemoteConnections I think it was called, but I didn't get anything from it.
mamaich said:
I've already posted a method that should enable RDP here: http://forum.xda-developers.com/showpost.php?p=36386089&postcount=211 - no need to patch DLL, and would work on an a locked device. But you'll have to manually edit binary registry value, instead of using a provided tool.
I have not tested RDP, but after using this method I was able to recover an option of joining device to Active Directory domain (it was blocked by the similar policies).
Click to expand...
Click to collapse
Again, please if you were able to join an RT to the domain. Please let me know what you did. Would love to not get prompted to log in into PowerShell.
apatcas said:
Again, please if you were able to join an RT to the domain. Please let me know what you did. Would love to not get prompted to log in into PowerShell.
Click to expand...
Click to collapse
As I've already wrote - use this method: http://forum.xda-developers.com/showpost.php?p=36386089&postcount=211
1. Edit registry:
Code:
HKEY_LOCAL_MACHINE\SYSTEM\Setup
SetupType=1
CmdLine="cmd.exe"
and reboot. You will enter the setup mode. You would not see the mouse cursor in this mode, and you'll need a hardware keyboard.
2. Open this reg_binary value: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ProductOptions\ProductPolicy. Look for unicode string "WorkstationService-DomainJoinEnabled", it is near offset 0x4000. Look at this screenshot:
http://imageshack.us/photo/my-images/526/35796208.png/
Select the "00" byte that follows the zero byte after the 64 (64 00 == unicode "d" letter) as you see on the screenshot. Overwrite it with 01. Be careful not to insert a byte, you need to overwrite the existing byte!
3. Rename sppsvc.exe to anything else so that it would not run on boot and reset ProductPolicy ("ren sppsvc.exe sppsvc.bak")
4. Reboot. Now the option to join the domain would be available.
I have not tried to add workstation to domain myself - try that and post here. After adding to domain you may try to rename sppsvc.bak back to sppsvc.exe as otherwise you'll get the "unactivated" Windows RT. I think that this would only remove the add to domain UI, but the RT would be still domain-joined.
I've tried to edit the remote desktop settings keys - this unblocked the corresponding options in the computer settings, but I was unable to connect. Maybe this is due to absence of RDP code in terminal server service - I don't see anyone listening port 3398 though TermServer service is running.
mamaich said:
As I've already wrote - use this method: http://forum.xda-developers.com/showpost.php?p=36386089&postcount=211
1. Edit registry:
Code:
HKEY_LOCAL_MACHINE\SYSTEM\Setup
SetupType=1
CmdLine="cmd.exe"
and reboot. You will enter the setup mode. You would not see the mouse cursor in this mode, and you'll need a hardware keyboard.
2. Open this reg_binary value: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ProductOptions\ProductPolicy. Look for unicode string "WorkstationService-DomainJoinEnabled", it is near offset 0x4000. Look at this screenshot:
http://imageshack.us/photo/my-images/526/35796208.png/
Select the "00" byte that follows the zero byte after the 64 (64 00 == unicode "d" letter) as you see on the screenshot. Overwrite it with 01. Be careful not to insert a byte, you need to overwrite the existing byte!
3. Rename sppsvc.exe to anything else so that it would not run on boot and reset ProductPolicy ("ren sppsvc.exe sppsvc.bak")
4. Reboot. Now the option to join the domain would be available.
I have not tried to add workstation to domain myself - try that and post here. After adding to domain you may try to rename sppsvc.bak back to sppsvc.exe as otherwise you'll get the "unactivated" Windows RT. I think that this would only remove the add to domain UI, but the RT would be still domain-joined.
I've tried to edit the remote desktop settings keys - this unblocked the corresponding options in the computer settings, but I was unable to connect. Maybe this is due to absence of RDP code in terminal server service - I don't see anyone listening port 3398 though TermServer service is running.
Click to expand...
Click to collapse
Joined... Nice find.
apatcas said:
Joined... Nice find.
Click to expand...
Click to collapse
Have it remained domain-joined after restoring the original sppsvc.exe?
You have to return it back, otherwise you'll be annoyed with the activation reminders.
mamaich said:
Have it remained domain-joined after restoring the original sppsvc.exe?
You have to return it back, otherwise you'll be annoyed with the activation reminders.
Click to expand...
Click to collapse
We could possibly patch sppsvc to not check, then start the service up after jailbreaking it.
I'm honestly not sure if this would be considered piracy or not, though.
Edit: I used the program to set every value to 1 in setup mode (The latest jailbreak tool works in setup mode), and I didn't see any change for anything dealing with RDP.
Edit 2: Perhaps I shouldn't have set 'Disable' to 1. Regardless, I set it to 0 and the options popped up, but I can't get anything to go. As mamaich stated, I'm not seeing anything listening on port 3389. netstat -a -b on a desktop with it enabled says it's opened by CryptSvc, but I'm not seeing anything with CryptSvc that's not there on the tablet. That could just be netstat guessing which service running under svchost is actually running it, too.
netham45 said:
We could possibly patch sppsvc to not check, then start the service up after jailbreaking it.
I'm honestly not sure if this would be considered piracy or not, though.
Edit: I used the program to set every value to 1 in setup mode (The latest jailbreak tool works in setup mode), and I didn't see any change for anything dealing with RDP.
Edit 2: Perhaps I shouldn't have set 'Disable' to 1. Regardless, I set it to 0 and the options popped up, but I can't get anything to go. As mamaich stated, I'm not seeing anything listening on port 3389. netstat -a -b on a desktop with it enabled says it's opened by CryptSvc, but I'm not seeing anything with CryptSvc that's not there on the tablet. That could just be netstat guessing which service running under svchost is actually running it, too.
Click to expand...
Click to collapse
I think we must hack the dll file.But I find when I edit a byte in the dll,the service was not able to start.
apatcas said:
Joined... Nice find.
Click to expand...
Click to collapse
So is it true? that your device stays domain-joined after you restore sppsvc.exe?
@ Netham45, you could try to open up W81x86 termsrv.dll and go to these hex locations to find out what functions needed patching.
Hashes
File: W81x86\termsrv.dll
CRC-32: 202cd912
MD4: a879d39b8fbcd968b525af05a66aaf2c
MD5: 7a8e1158291cf4c8d8474a2091b9bf6d
SHA-1: e10028b074d24605e05b5e0bafd42f6a93ac01ad
1550F-15520
17428
A1B29
Then go into WinRT termsrv.dll, jump to those functions by name (because offsets will be different between x86 and RT) and Jmp or Nop as needed for WinRT. Afterwords it could be added via CDB / KD on-the-fly.
MICROSOFT.WINDOWS.RT.8.1.WITH.OFFICE.2013.RT.RTM.WOA.ENGLISH.DVD-WZT
MICROSOFT.WINDOWS.RT.8.1.ADK.KIT.WOA.RTM-WZT
Thats all I want to say
windowsrtc said:
MICROSOFT.WINDOWS.RT.8.1.WITH.OFFICE.2013.RT.RTM.WOA.ENGLISH.DVD-WZT
MICROSOFT.WINDOWS.RT.8.1.ADK.KIT.WOA.RTM-WZT
Thats all I want to say
Click to expand...
Click to collapse
Anyone tried it yet? Looks like a risky process.
windowsrtc said:
MICROSOFT.WINDOWS.RT.8.1.WITH.OFFICE.2013.RT.RTM.WOA.ENGLISH.DVD-WZT
MICROSOFT.WINDOWS.RT.8.1.ADK.KIT.WOA.RTM-WZT
Thats all I want to say
Click to expand...
Click to collapse
Thanks. Unfortunately, what I gather from what I'm reading is that that image does not contain drivers. You need to manually add the drivers to the image before you install. If you don't, you'll brick your tablet, according to WZT. People may want wait a little bit until there are clear directions and a few people who can verify that they worked (i.e. that they installed 8.1 without any problems).
Additional note: It sounds like the driver package is only for the Surface RT, so users with other Windows RT tablets (ex. ASUS VivoTab RT) may brick their tablets if they try to use it. They'll have to wait until someone releases a driver package for their model (which WZT says might have to be taken from the Preview build).
Osprey00 said:
Even more unfortunately, while WZT has teased info about the driver package, they haven't actually leaked it yet.
Click to expand...
Click to collapse
This part isn't actually true, for what it's worth- it's included with the main download.
jhoff80 said:
This part isn't actually true, for what it's worth- it's included with the main download.
Click to expand...
Click to collapse
Oh, OK. I didn't catch that. They made it appear as though it was a separate download. Ah, you're right: there they are.
just run setup.exe
all drivers for surface are build in
BTW:I have rollback to 8.0 again
Osprey00 said:
...users with other Windows RT tablets (ex. ASUS VivoTab RT) may brick their tablets if they try to use it.
Click to expand...
Click to collapse
It is very difficult to brick an RT device. You can always recover it if you can boot to USB, and you have a recovery image and familiar with windows command line tools (diskpart, dism and so on).
Unfortunatley I'm on a business trip and can't create an upgrade instruction for VivoTab users. But there is nothing difficult - as we already have all needed drivers on a recovery partition, and all you need - just insert them into WIM using the Wzor's instructions from his original post on ru-board.
Installed this tonight. Note that drivers are NOT included in the iso from Wzor.
Extract boot.wim and install.wim from Wzor's iso, inject Wzor's RTM drivers via dism, commit, put boot.wim and install.wim with drivers back into iso, image to USB drive. I installed from within RT using setup (keeping nothing).
You have to use the default key on installation. You need to find out your actual RT key before you do this otherwise you end up with a non-activated RT 8.1 and no key. Export DigitalProductId and DigitalProductId4 from HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion and obtain your key. Instructions on how to here.
Works great. In the short amount of time I've been testing everything works perfectly OK, including all my accessories. (discussion here).
mamaich said:
It is very difficult to brick an RT device. You can always recover it if you can boot to USB, and you have a recovery image and familiar with windows command line tools (diskpart, dism and so on).
Click to expand...
Click to collapse
I figured as much, but not everyone may have the recovery image or the knowledge, and, for them, a dead device that they're unable to recover is as good as a brick. Regardless, I just wanted to pass along the same language that WZT used so that I'm not guilty of misrepresenting the risks or responsible if someone can't fix what he got himself into.
derausgewanderte said:
Installed this tonight. Note that drivers are NOT included in the iso from Wzor.
Extract boot.wim and install.wim from Wzor's iso, inject Wzor's RTM drivers via dism, commit, put boot.wim and install.wim with drivers back into iso, image to USB drive. I installed from within RT using setup (keeping nothing).
You have to use the default key on installation. You need to find out your actual RT key before you do this otherwise you end up with a non-activated RT 8.1 and no key. Export DigitalProductId and DigitalProductId4 from HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion and obtain your key. Instructions on how to here.
Works great. In the short amount of time I've been testing everything works perfectly OK, including all my accessories. (discussion here).
Click to expand...
Click to collapse
Thanks for your instructions and verifying that it works. The original instructions don't mention writing down your current key first. While I likely would've done that anyways, it's re-assuring to see it in writing, just in case. I might give this a go tomorrow.
FYI, there's now an ISO with the Surface RT drivers baked in, so that users don't have to use DISM to add them manually. The release name is:
DRIVERS FOR SURFACE RT ONLY___MICROSOFT WINDOWS RT 8 1 WITH OFFICE 2013 RT RTM WOA ENGLISH DVD-WZT
Note that it's only for the Surface RT, not other RT tablets.
Also note that you need the installation key, and, also, before installation, you need to export and decrypt your retail 8.0 key. Information on that is available here
Osprey00 said:
Also note that you need the installation key, and, also, before installation, you need to export and decrypt your retail 8.0 key. Information on that is available here
Click to expand...
Click to collapse
and here is the direct link to Osprey00's post with a way of getting the key if you only have your RT.
Good news!
I'll just wait till some skillful surface owner gets the jailbreak and then update!
huslterose said:
Good news!
I'll just wait till some skillful surface owner gets the jailbreak and then update!
Click to expand...
Click to collapse
[EDIT: Never mind. I misunderstood.]
I don't follow. There's nothing to "jailbreak" and it can't get much easier than it is now (outside of simply waiting until Microsoft rolls out 8.1 via Automatic Updates). You just follow instructions to find out your 8.0 key, install the 8.1+drivers ISO (not the one in the OP; the one that I listed a few posts up) with a general installation key, then activate 8.1 with your 8.0 key.
Osprey00 said:
I don't follow. There's nothing to "jailbreak" and it can't get much easier than it is now (outside of simply waiting until Microsoft rolls out 8.1 via Automatic Updates). You just follow instructions to find out your 8.0 key, install the 8.1+drivers ISO (not the one in the OP; the one that I listed a few posts up) with a general installation key, then activate 8.1 with your 8.0 key.
Click to expand...
Click to collapse
I think he is referring to the lack of jailbreak on 8.1 for unsigned desktop apps - a feature which should have been in the OS from the start, instead microsoft wasted time patching the exploit the jailbreak used and destroyed the usefulness of the tablet for some.
He was probably intending to say something along the lines of him not updating to 8.1 until after someone makes a new jailbreak for it.
If you can live without the jailbreak, thats fine. Windows store is a bit too limited in my opinion, but it will grow (still gutted they blocked access to both localhost for network connections and COM ports in windows apps though).
SixSixSevenSeven said:
I think he is referring to the lack of jailbreak on 8.1 for unsigned desktop apps - a feature which should have been in the OS from the start, instead microsoft wasted time patching the exploit the jailbreak used and destroyed the usefulness of the tablet for some.
He was probably intending to say something along the lines of him not updating to 8.1 until after someone makes a new jailbreak for it.
If you can live without the jailbreak, thats fine. Windows store is a bit too limited in my opinion, but it will grow (still gutted they blocked access to both localhost for network connections and COM ports in windows apps though).
Click to expand...
Click to collapse
Ah! Gotcha. It slipped my mind that the jailbreak for unsigned apps not working in 8.1 is a valid reason for not upgrading, so I was thinking that he was waiting for something to make the upgrade, itself, even easier. Thanks for the clarification.
@Osprey00 - is there a direct link perhaps
aooga said:
Could someone please post instructions on how to decrypt the registry values? The link that was posted is down. Thanks.
Click to expand...
Click to collapse
Sure. There are a few different ways to do it. In order of simplest to most complicated...
METHOD 1 - Can be done solely from Windows RT (any version):
1. Follow these instructions to create a batch file.
2. Run the batch file on the tablet to get your key.
3. Either write the key down or right-click anywhere in the window, select Mark, highlight the key, right-click again (which will copy the key to the clipboard), paste the key into a text file and then copy that text file to another computer or backup drive.
4. Optional, but recommended: Check that the key is valid by inputting it into a key checker, such as The Ultimate PID Checker. If it tells you that the key is invalid, then try one of the other two methods.
METHOD 2 - Requires regular, non-RT Windows (XP/Vista/7/8):
1. In RT, open the charms bar, click Search, enter "Regedit" and run Regedit.
2. Export HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion to a .reg file.
3. Copy that .reg file to your non-RT Windows.
4. On your non-RT Windows (all remaining steps will be done there), right-click the .reg file and choose Edit. Change "CurrentVersion" to "CurrentVersionRT". Re-save the file.
5. Double-click on the .reg file and import it.
6. Download and install WinTK.
7. Run WinTK, paste "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersionRT" (without quotes) into the field and press the Decrypt button.
*If, for some reason, WinTK won't run, you can try this: download and unzip Produkey, run Regedit, export your CurrentVersion key to a backup .reg file, change the key name in your RT .reg file from "CurrentVersionRT" back to "CurrentVersion", remove all values in your RT .reg file except for DigitalProductId and DigitalProductId4 (make sure that they're NOT the ones under the DefaultProductKey sub-branch), import that (thus overwriting your Windows key with your Windows RT key), run Produkey, write down the Product Key, then import the backup .reg file to restore your Windows key (important, obviously).
8. Write down the product key.
9. Optional, but recommended: Check that the key is valid by inputting it into a key checker, such as The Ultimate PID Checker. If it tells you that the key is invalid, then try one of the other two methods.
10. Optional: Open Regedit again and delete the CurrentVersionRT key, just to clean up.
METHOD 3 - Can be done solely from Windows RT, but only on 8.0 (won't work on 8.1 Preview or 8.1 RTM) and is more complicated than Method 1:
1. Download and unzip the RT jailbreak tool.
2. Run RunExploit.bat. Choose 'R' from the menu. Let it finish, then press any key when it asks you to.
3. Download and install Win86emu.
4. Download and unzip Produkey.
5. Open the charms bar, click Search, enter "Regedit" and run Regedit.
6. Export HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion to a .reg file.
7. Find the Win86emu tile (icon is "x86") on your Start screen, flick down on it to bring up the options bar and tap Open File Location... or, at the Desktop, you can browse to C:\ProgramData\Microsoft\Windows\StartMenu\Programs\win86emu.
8. Double-tap the "x86 Registry Editor" shortcut.
9. In that registry editor, import the .reg file that you exported in step 4. This will import the settings into the special x86 registry that the emulator created when you installed it and which all x86 programs (including Produkey) will think is the real registry.
10. Double-tap the "Run x86 Program" shortcut.
11. Browse to and select the produkey.exe that you unzipped in step 2.
12. Find the Product Key listed for Windows in the window that appears and write it down. If nothing appears, click on Select Source and verify that it's searching the local computer (top-most radio button).
13. Optional, but recommended: Check that the key is valid by inputting it into a key checker, such as The Ultimate PID Checker. If it tells you that the key is invalid, then try one of the other two methods.
If one method doesn't seem to work for you, try one of the others.
Osprey00 said:
Sure. There are a few different ways to do it. I'll describe two...
...
Hopefully, I didn't forget any steps from either of those methods.
Click to expand...
Click to collapse
Thanks!. Now just waiting to download the iso. Its taking an age.
EDIT: mydigitallife was hacked...thats why the links are down.
aooga said:
Thanks!. Now just waiting to download the iso. Its taking an age.
EDIT: mydigitallife was hacked...thats why the links are down.
Click to expand...
Click to collapse
thanks for the info. was about to search for reasons. hacked by MS?
derausgewanderte said:
thanks for the info. was about to search for reasons. hacked by MS?
Click to expand...
Click to collapse
Yeah I was clueless why it wasn't working, so I just looked at their facebook page.
Would putting a link like this on XDA be considered warez? If not, can someone who has already downloaded the ISO with drivers upload it somewhere? There is no way I'm waiting till Oct. 16