Related
I just downloaded and installed and after soft reset it shows an error saying ...
"An unexpected error has occurred in WindowsMobileCallBlockSrv.exe. Select quit and then restart this program, or select Details for more information.
This application requires a newer version of the Microsoft .NET. Compact Framework than the version installed on this device."
Any ideas how to get it to install? I created a support ticket with the makers at SynergTech Solution website I got it and they haven't responded. I did it yesterday. I think they don't really have any support.
I also noted there is a 1.5 somewhere on the internet but can't figure out how to dl it. Don't know if this helps.
Palm Treo Pro Windows Mobile 6.1 Pro stock Sprint
I guess I could have put this in the General subforum instead. If a mod wants to move it, please do.
Over the past month or so, I have heard stories of people choosing the wrong language options when they used Seven-Eighter to update their windows phone device and having problems after the procedure is over. Well, there is now hope for those people.
I have made a program which will allow you to restore language packs that you forgot to choose when you ran Seven-Eighter (either my version or the original version) to update your windows phone device. Instructions and download link can be found on my blog. I am sure that it is just as easy to use as my version of Seven-Eighter.
link to blog post: http://bit.ly/16Lv2iq
I am always looking to improve. I welcome any and all suggestions. If you want to throw something my way to help with development you are welcome to do so (just use the donate button next to my name on this post), but not required (your satisfaction works just as well).
Any tricks to using your app? When I launch it, I don't see any visual indicator that its running. There is a brief xmlmfile that gets created, but it never seems to have any content. Seven eighter itself runs fine.
Using Windows 8 x64.
Thanks for putting this out there, trying to recover my Phone now
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
i want to install windows 10 iot and I have a Windows RT tablet. I successfully performed downgrade from 8.1 to 8.0. The former owner when sat on Windows 8.1 RT said that he was not updated. That's nice. After creating the second user, I started trying to perform secureboot debug. In the account policy I created another user and assigned to him all the roles, including administrator, User Replicator, etc. After that I managed to run the script and on a black background to press the treasured inscription "Accept and install". After the download, I ran the command that was in the Readme file from the Secureboot folder. After that I started to prepare a flash drive. Build ffu file Windows 10 IoT as a person from the video ( https://youtu.be/ivwuxBR96oE ) I mounted through the command DISM /mount-ffu. After that I added the files efi to download, but unfortunately further I did not succeed in doing anything. By the way I install a jailbreak. When you try to boot from a prepared SD card, it ignores it. All the methods are tried. What could be wrong? i may to record video
mickel52 said:
i want to install windows 10 iot and I have a Windows RT tablet. I successfully performed downgrade from 8.1 to 8.0. The former owner when sat on Windows 8.1 RT said that he was not updated. That's nice. After creating the second user, I started trying to perform secureboot debug. In the account policy I created another user and assigned to him all the roles, including administrator, User Replicator, etc. After that I managed to run the script and on a black background to press the treasured inscription "Accept and install". After the download, I ran the command that was in the Readme file from the Secureboot folder. After that I started to prepare a flash drive. Build ffu file Windows 10 IoT as a person from the video (
) I mounted through the command DISM /mount-ffu. After that I added the files efi to download, but unfortunately further I did not succeed in doing anything. By the way I install a jailbreak. When you try to boot from a prepared SD card, it ignores it. All the methods are tried. What could be wrong? i may to record video
Click to expand...
Click to collapse
There is no advantage to running W10IOT on your surface. Why do you want to? You'll get more use out of jailbroken windows RT
Qiangong2 said:
There is no advantage to running W10IOT on your surface. Why do you want to? You'll get more use out of jailbroken windows RT
Click to expand...
Click to collapse
I want launch my uwp app and put on my room surface rt for management automatization my house!
Hi everyone!
I know thousands of tutorials have been already made for the Surface RT/2, they are not often updated, are missing important steps or are not covering common errors occurring while doing this procedure, leaving the user wondering what to do next.
My tutorial will not be on this post, because of the limited layout options of an XDA post/thread.
Here is the tutorial: https://www.alexenferman.com/articles/SurfaceRT/W10-OA-SurfaceRT
This tutorial covers: The installation process, Pictures, Possible errors and solutions, Extras
I also made a video.
https://www.youtube.com/watch?v=yzFqbBDKeXw
Comments or questions can be posted on this thread or in the comments section at the bottom section of the website.
Enjoy!
I followed this tutorial and I have windows 10 now. Still have question, why web browsing suck that much? It is incredibly slow.
In you tutorial you mention a build update using "install.ps1" I did not found that file in the zip.
Thank you again, great work you have there
fefetron said:
I followed this tutorial and I have windows 10 now. Still have question, why web browsing suck that much? It is incredibly slow.
In you tutorial you mention a build update using "install.ps1" I did not found that file in the zip.
Thank you again, great work you have there
Click to expand...
Click to collapse
I know, browsing is slow.
Well, in this case, you will have to open each file and click on "install"
I am using store.rg-adguard to download apps. Some of them are asking for Microsoft.vcliba.1100.00 arm. I have found x86 and x64 over internet but not arm. Do you have it? Thank you man.
Found it in "store.rg-adguard.net" thank you
Hi Alex,
I have read your instructions and most of the commends.
Very interesting and I am eager to give it a try.
One question though,
In the meantime my Surface RT is version 8.1 and even has the start items in a row on the left side, as in windows 10.
Should i go back to version 8.0 to start your Windows 10 upgrade?, or can I start from the present situation.
Your help is much appreciated.
Regards, Hans
Hi Alex,
your tutorial worked great for me. Thank You.
Just one more thing: After starting windows I do get an error like "Windows created a temporary paging file". So I thought maybe pagefile.sys is corrupt. I was no able to clean this. After sfc /scannow it tells me corrupt files are found but no correction was possible.
Maybe you have another idea.
Best Regards Tom
Install Microsoft.NET.Native.Runtime.1.1.appx
Hi Alex,
At the end of your amazing tutorial it says:
Install Microsoft.NET.Native.Runtime.1.1.appx and the other one.
Can you explain how to install these files?
Clicking on them has no effect.
Regards,
Hans
658731
Works wonders, thank you very much!
Only problem I have is this "paging error" whenever I log in, which I couldn't seem to be able to fix even though I tried optimizing the W10 setting a few different ways. Do you have any suggestion?
Thank you again!
EDIT: I set it manually to max size (min 16 MB, max 2047 MB) and the error is gone!
thanks! that worked for me
had to do it twice though with two reboots
anyways solved!
Paaltjes said:
Hi Alex,
At the end of your amazing tutorial it says:
Install Microsoft.NET.Native.Runtime.1.1.appx and the other one.
Can you explain how to install these files?
Clicking on them has no effect.
Regards,
Hans
658731
Click to expand...
Click to collapse
Did you run APPX.ps1 in the APPX.rar before trying to install the .net runtime?
tomekkdagost said:
Hi Alex,
your tutorial worked great for me. Thank You.
Just one more thing: After starting windows I do get an error like "Windows created a temporary paging file". So I thought maybe pagefile.sys is corrupt. I was no able to clean this. After sfc /scannow it tells me corrupt files are found but no correction was possible.
Maybe you have another idea.
Best Regards Tom
Click to expand...
Click to collapse
You have to create the pagefile yourself. I forgot to add it in my tutorial. Will add it soon. Meanwhile, search for "how to make pagefile Windows" or something like that.
alexenferman said:
Did you run APPX.ps1 in the APPX.rar before trying to install the .net runtime?
Click to expand...
Click to collapse
Yes, I did.
In the meantime I found a solution for the 2 files.
I transferred them to my user direction and from there with the Powershell I could install them.
Thanks for your help. Regards,
Hans
Hello,
Thanks for the tuto and the video
I went through the instructions but after applying the win 10 image, the boot will lead to automatic repair.
Trying the reset, show only 8.1 in the list of operating systems
Did I mess up in the process ? Should I start over again ?
Thanks
Hi Alex, didn't realize you had a thread for the tutorial here as well. i asked on yt/page about my issue:
I'm stuck at the end. After I installed the Chinese wim 'successfully', I reboot it and the Surface shows blue screen error 0xc000000f and if I press the windows logo button on the tablet I get the 0xc0000428 error. The fix on the website doesn't work, when I go into "Troubleshooting", then select "Reset this PC" then select 8.1rt and there it gives me a msj saying 'insert your windows installation or recovery media to continue" The usb img last used did not work, tried putting the install wim from 8.1 image (SurfaceRT_BMR_30.8.17.0) and get the same message about 'insert your windows. Thanks for the tutorial!
The file in the Google drive folder is named "windows RT surface 1 (RT). wim"
Is that the name that should be entered on dism apply image command? System doesn't recognise install.wim and I don't have that file on my USB
diskpart exit ..then problem
I have followed your directions and ran into a problem. After diskpart> exit (enter)
Yours shows x:\Sources
Mine shows
x:Windows\system32>
Where is my issue? I am on Windows 8.1. Do I need to go back to 8.0?
Appreciate your time
Thank you very much . you gave me a new hope for my Rt1
if you need any test device for any modification just ask.
heathersonline said:
The file in the Google drive folder is named "windows RT surface 1 (RT). wim"
Is that the name that should be entered on dism apply image command? System doesn't recognise install.wim and I don't have that file on my USB
Click to expand...
Click to collapse
You need to rename the file to install.wim or any other name you want, then you can type the command with the filename you chose.
Hello,
I am stuck on step 2. After having successfully installed the corrected Windows RT image, I restart my tablet (Surface RT) and I am stuck on the "Region and Language" choice screen. The tablet no longer reacts (no touch screen, no keyboard, etc.).
Do you have a solution ?? Thank you
Gooal81 said:
Hello,
I am stuck on step 2. After having successfully installed the corrected Windows RT image, I restart my tablet (Surface RT) and I am stuck on the "Region and Language" choice screen. The tablet no longer reacts (no touch screen, no keyboard, etc.).
Do you have a solution ?? Thank you
Click to expand...
Click to collapse
I think you installed the wrong image. People tend to install the Surface RT image on the Surface 2. In this case, simply install the Surface 2 wim and touch and keyboard will work again.