Related
All,
Please find the attached Windows RT native binaries for Snes9x 1.53. Snes9x is a SNES emulator.
http://snes9x.ipherswipsite.com/
I've had to disable a few features, such as OpenGL support and AVI recording. Direct 3D support is still there and I've included the D3D9 runtime in the package. Please don't ask me for ROMs - google is your friend. I've tried a couple roms, seems to be working just fine, but there could be issues lurking as there were lots of compilation warnings.
Also, I don't have an Xbox controller handy so I'm not sure how well that will work.
Cheers!
EDIT: before anyone slams me for the port.. yes I'm aware of "Snes8x" in the app store
bfosterjr said:
All,
Please find the attached Windows RT native binaries for Snes9x 1.53. Snes9x is a SNES emulator.
http://snes9x.ipherswipsite.com/
I've had to disable a few features, such as OpenGL support and AVI recording. Direct 3D support is still there and I've included the D3D9 runtime in the package. Please don't ask me for ROMs - google is your friend. I've tried a couple roms, seems to be working just fine, but there could be issues lurking as there were lots of compilation warnings.
Also, I don't have an Xbox controller handy so I'm not sure how well that will work.
Cheers!
EDIT: before anyone slams me for the port.. yes I'm aware of "Snes8x" in the app store
Click to expand...
Click to collapse
nice job!work well on my surface:good:
thank you nice work!
bfosterjr said:
EDIT: before anyone slams me for the port.. yes I'm aware of "Snes8x" in the app store
Click to expand...
Click to collapse
It's funny, because when you first posted this port I had that thought, but I downloaded it anyway. I have since discovered I cannot freaking play Super Mario with the store version's touch controller... it's just to imprecise (and no feedback) for me to actually have fun playing Mario (i.e. not dying constantly), and unless I'm just missing something, it doesn't seem to support keyboard input. So your port of Snes9x to the rescue! Thank you! I am curious what your motivation was to port it...
domboy said:
It's funny, because when you first posted this port I had that thought, but I downloaded it anyway. I have since discovered I cannot freaking play Super Mario with the store version's touch controller... it's just to imprecise (and no feedback) for me to actually have fun playing Mario (i.e. not dying constantly), and unless I'm just missing something, it doesn't seem to support keyboard input. So your port of Snes9x to the rescue! Thank you! I am curious what your motivation was to port it...
Click to expand...
Click to collapse
open charms bar, settings, there's something in there to enable and disable hardware or touch controls etc.
I guess some people prefer desktop apps to modern UI, that and its always a nice exercise.
domboy said:
... I am curious what your motivation was to port it...
Click to expand...
Click to collapse
I dream of a world where Metro doesn't exist ....
SixSixSevenSeven said:
open charms bar, settings, there's something in there to enable and disable hardware or touch controls etc.
I guess some people prefer desktop apps to modern UI, that and its always a nice exercise.
Click to expand...
Click to collapse
Ahh, charms bar... I was looking in the um, "swipe from the bottom of the screen"...
bfosterjr said:
I dream of a world where Metro doesn't exist ....
Click to expand...
Click to collapse
Works for me... the longer I've had my Surface, the more I prefer the desktop for many things. So thanks again!!
Yeah there Is no Xbox controller support, unfortunately. Very solid port otherwise, thanks for the effort,
Having issues running this on 8.1.
Any suggestions? Just pops up a Windows error.
callmechewy said:
Having issues running this on 8.1.
Any suggestions? Just pops up a Windows error.
Click to expand...
Click to collapse
*facepalm* there are many threads and posts saying how there is no jailbreak for 8.1, this requires the jailbreak, therefore you cant use it. Snes8x is on the windows store though.
SixSixSevenSeven said:
*facepalm* there are many threads and posts saying how there is no jailbreak for 8.1, this requires the jailbreak, therefore you cant use it. Snes8x is on the windows store though.
Click to expand...
Click to collapse
Sorry, it doesn't say anywhere that it requires jailbreak, so I didn't think about it.
I'll start assuming it requires jailbreak if it's not in the Store. Safe enough assumption?
callmechewy said:
Sorry, it doesn't say anywhere that it requires jailbreak, so I didn't think about it.
I'll start assuming it requires jailbreak if it's not in the Store. Safe enough assumption?
Click to expand...
Click to collapse
yes. the idea of the jailbreak is that windows RT will only run apps if they have a digital signature from microsoft, which is not something they are issuing for desktop apps so our apps ports do not have a signature and will not run on windows RT. The jailbreak removed that restriction so it will run desktop apps developed by us (internet explorer, microsoft office and the other apps already on the device being microsoft apps are signed so will run on non jailbroken systems). Only microsoft can sign the apps.
There are a few exceptions, bat scripts can run on RT without a jailbreak, I think powershell scripts are fine too. You can coerce it into playing .swf files too (in metro too actually). Anything else, jailbreak required.
Sadly the exploit the jailbreak used was patched by microsoft in 8.1, why? we don't know. It serves no purpose to lock the desktop in this way and they went right out of their way to change the signature enforcement seemingly just to prevent the jailbreak. I think a few people have hinted at ways to jailbreak 8.1, but so far the idea has been to keep your mouth shut if you have an idea and only share via private means so that microsoft can't patch it until its too late (october when 8.1 goes fully public), as a result I have no idea if there is any progress, officially there is not.
Since the whole point of the jailbreak is to enable running non-"app" software, yes, that's a pretty safe assumption (not perfect - sideloaded apps don't need a jailbreak - but anything that tells you to run an EXE will).
SixSixSevenSeven said:
Sadly the exploit the jailbreak used was patched by microsoft in 8.1
Click to expand...
Click to collapse
This is only kind of true. The kernel exploit itself, the lack of validation on the object pointer on NtUserSetInformationThread subfunction 7, was not fixed. Getting to it was fixed and/or made much harder.
bfosterjr said:
All,
Please find the attached Windows RT native binaries for Snes9x 1.53. Snes9x is a SNES emulator.
http://snes9x.ipherswipsite.com/
I've had to disable a few features, such as OpenGL support and AVI recording. Direct 3D support is still there and I've included the D3D9 runtime in the package. Please don't ask me for ROMs - google is your friend. I've tried a couple roms, seems to be working just fine, but there could be issues lurking as there were lots of compilation warnings.
Also, I don't have an Xbox controller handy so I'm not sure how well that will work.
Cheers!
EDIT: before anyone slams me for the port.. yes I'm aware of "Snes8x" in the app store
Click to expand...
Click to collapse
Do you happen to have the sources and project files available? I'd like to build upon yours and try to integrate with XInput as done by snes8x, specifically CBoxController.c/h, ControllerInput.c/h, etc.
How about buld new 1.55 release for WinRT?
https://github.com/snes9xgit/snes9x
I miss also DMGBoy latest 2.0 version build.
All,
First, let me say that this is not a jailbreak tool for RT 8.1! All clear? Good.
I've written a simple little driver and exe tool to patch the g_CiOptions and SeILSigningPolicy variables in ci and ntos. The obvious kicker is that you need the driver loaded for this to work -- but once loaded you can effectively use this to turn on/off the signing at will (eg: useful to avoid -- not disable -- patch guard).
I've tested this on my Surface RT as well as Windows 8 without issue.
You can find the code and binaries on github ( https://github.com/bfosterjr/ci_mod ). There isn't a whole lot of documentation (nearly zero), but you'll find batch files, windbg scripts, and various other bits which should help you figure out how it works (or you can just read the code).
Now, before you all flame me about how useless this is without a jailbreak or kernel execution for RT 8.1, let me say this: I've spent the last few days catching up on a lot of threads (over a years worth) in this form and there is enough information (if you look hard enough, open your mind, and tilt your head) in the threads to successfully start your own driver on 8.1 RT.
Cheers!
Any hint please?
Note that I would not recommend leaving this hack enabled on 8.1 once whatever programs are loaded. This will set off PatchGuard and the system will bluescreen. Enable it, run whatever, then disable it. Most programs should be OK once fully started to leave running with the hack disabled. Only loading unsigned DLLs from that point on would mess up.
8.0, do whatever; doesn't matter.
Melissa
Myriachan said:
Note that I would not recommend leaving this hack enabled on 8.1 once whatever programs are loaded. This will set off PatchGuard and the system will bluescreen. Enable it, run whatever, then disable it. Most programs should be OK once fully started to leave running with the hack disabled. Only loading unsigned DLLs from that point on would mess up.
8.0, do whatever; doesn't matter.
Melissa
Click to expand...
Click to collapse
Quite right - which is why the ci_mod program I wrote will run indefinitely waiting for user input to toggle on, or off, the kernel patching. So.. (1) Load the driver which will immediately toggle patching ON... (2) start ci_mod.exe and toggle patching back OFF ... (3) leave ci_mod.exe running. Doing so you will always re-toggle patching on (then off again) so you can run your unsigned app with minimal likelihood of PatchGuard being a problem.
Hopefully that makes sense.
Obviously, if anyone wants to make changes to the driver or program -- perhaps to alter it to suit initial driver execution conditions -- they're welcome too -- the code is GPL.
Cheers!
LolitaPlus said:
Any hint please?
Click to expand...
Click to collapse
Sorry no. There are serious reasons why I can't explain further. So please don't ask.
But trust me.. the bits you need are there... you just need to stitch them together.
bfosterjr said:
Sorry no. There are serious reasons why I can't explain further. So please don't ask.
But trust me.. the bits you need are there... you just need to stitch them together.
Click to expand...
Click to collapse
Hai, I'm kinda new to this whole hacking scene especially to the x86/x64 bit one (has been working on arm for a little while) and I was wondering what knowledge was necessary to be able to glue everything together? Which glue I need to use so to say
Thanks.
filfat said:
Hai, I'm kinda new to this whole hacking scene especially to the x86/x64 bit one (has been working on arm for a little while) and I was wondering what knowledge was necessary to be able to glue everything together? Which glue I need to use so to say
Thanks.
Click to expand...
Click to collapse
Years of Windows internals/development/debugging makes for good glue. That and the general desire (and patience) to want to mess with software....
bfosterjr said:
...
You can find the code and binaries on github ( https://github.com/bfosterjr/ci_mod ). ...
Click to expand...
Click to collapse
Hey mate, this looks very nice and far more user(noob)-friendly. Thank you soo much for sharing. :good:
Cheers
Blade
P.S.:
1) Is your deleted sign.bat a kind of launcher which : toggle -> start app -> toggle ?
2) Is it possible to share the compiled version? [Don't want to bother you] (Just formated my dev-pc and set it up to compile Android 4.4.4 for my desire Z. I know i need a new pc with a bigger hdd) :crying:
BIade said:
Hey mate, this looks very nice and far more user(noob)-friendly. Thank you soo much for sharing. :good:
Cheers
Blade
P.S.:
1) Is your deleted sign.bat a kind of launcher which : toggle -> start app -> toggle ?
2) Is it possible to share the compiled version? [Don't want to bother you] (Just formated my dev-pc and set it up to compile Android 4.4.4 for my desire Z. I know i need a new pc with a bigger hdd) :crying:
Click to expand...
Click to collapse
Hey Blade!
1) nope. that was a batch file to test sign the driver. its not required. the toggling of the patching is done by the user through cimod.exe (runs in a continuous user-input loop)
2) binaries for all supported platforms are there already -- https://github.com/bfosterjr/ci_mod/tree/master/bin
Cheers!
It would be really cool to hook the CreateProcess and LoadLibrary calls such that, if the target binary is unsigned and the caller isn't in an appcontainer, the policy is (automatically) flipped juuuust long enough for the call to succeed, and then (automatically) flipped back. That means minimal risk of a BSOD and maximum user-friendliness.
I proposed this approach months ago on the JB discussion thread, but never got around to writing it. Now bfosterjr has written the driver part (probably by far the hardest part) in a few days! We missed you...
GoodDayToDie said:
It would be really cool to hook the CreateProcess and LoadLibrary calls such that, if the target binary is unsigned and the caller isn't in an appcontainer, the policy is (automatically) flipped juuuust long enough for the call to succeed, and then (automatically) flipped back. That means minimal risk of a BSOD and maximum user-friendliness.
I proposed this approach months ago on the JB discussion thread, but never got around to writing it. Now bfosterjr has written the driver part (probably by far the hardest part) in a few days! We missed you...
Click to expand...
Click to collapse
Thanks man. Really wasn't all that difficult. The driver isn't quite as flexible (or perfect) as it could be. To accomplish what you're suggesting might take some effort because, IIRC, the normal process create callbacks don't get triggered until after process image verification. I'll have to double check that.
I might take a stab at updating the driver to make it more automated. Once I have a bough free time. Stay tuned
Cheers!
bfosterjr said:
Thanks man. Really wasn't all that difficult. The driver isn't quite as flexible (or perfect) as it could be. To accomplish what you're suggesting might take some effort because, IIRC, the normal process create callbacks don't get triggered until after process image verification. I'll have to double check that.
I might take a stab at updating the driver to make it more automated. Once I have a bough free time. Stay tuned
Cheers!
Click to expand...
Click to collapse
What GoodDayToDie suggested is not using PsSetCreateProcessNotifyRoutineEx but hooking Ring3 API. I can offer some help if you need ARM Ring3 inline hook. I already wrote a hook engine though it is more like a POC.
LolitaPlus said:
What GoodDayToDie suggested is not using PsSetCreateProcessNotifyRoutineEx but hooking Ring3 API. I can offer some help if you need ARM Ring3 inline hook. I already wrote a hook engine though it is more like a POC.
Click to expand...
Click to collapse
Yeah, I got that.. but I'm just not a fan of hooking the be-jesus outta usermode to solve this problem. I don't' like hooking in general.. as it tends to just lead to more problems and complications. I'd rather try to find a more clever way to solve this problem with callbacks or some other OS supported mechanism.
Cheers!
Yeah... another option would be hooking NtCreateProcess (ring 0) either in the actual entry point or at the syscall table, but I can't imagine you're *more* enthusiastic about hooking kernel-mode than user-mode, and messing with the syscall table could make PatchGuard angry too. With that said, the user-mode hook would be pretty easy, actually; once the tool is running, it uses the process instrumentation/shimming stuff in Windows (ImageFileExecutionOptions key?) to have every EXE load a (homebrew) DLL at startup. The DLL installs the requisite hooks (and probably then unloads itself). You'd need to inject that DLL into already-running processes, but that's not hard.
Windows automation isn't my strong point, but I know the x86 emulation layer is able to detect when somebody tries to run an x86 EXE and intercept the attempt *before* the process launch fails. Is this usable here (i.e. does whatever that listens on trigger before the signature check)? If not, a hook may be the only workable approach, hacky though it is.
bfosterjr said:
there is enough information (if you look hard enough, open your mind, and tilt your head) in the threads to successfully start your own driver on 8.1 RT.
Cheers!
Click to expand...
Click to collapse
Well I've been looking, and contributing, for a long time, but still cant quite crack it ...
Can't quite understand
I have read through your source code. I don't quite understand the point though. Is this app and driver to allow unsigned exe to run? Is the batch file required? From what I can see all that is required is netham45's Jailbreak and this to run unsigned exe. I would like to share my finding's in an instruction post but thought I would ask your permission first. May I?
Thanks,
Wcomhelp
The purpose of this is to make it "safer" to jailbreak 8.1, since if you change the code integrity flag in 8.1 and leave it changed for any length of time, the system will crash due to PatchGuard. This driver is so you can only change the code integrity settings when you need to load unsigned code, giving minimal time for PatchGuard to notice and minimizing the risk of a crash.
HOWEVER, you cannot load this driver unless you already have unsigned code execution through some other means. That other means has not yet been published; if you want to use this tool you will need to figure out how to install it yourself (or wait for a published hack).
EDIT:
Wouldn't CVE-2014-4148 / CVE-2014-4113 (MS14-058) be sufficient to initially load this tool?
cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-4113
cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-4148
technet.microsoft.com/library/security/MS14-058
Yeeeeesssssss... yes it probably would!
Of course, you'd need to avoid installing the patch for it - not really a "proper" jailbreak, in that sense - but yeah, that should work. All you need to do is toggle code signing off for a second to load the driver, and code execution in Win32k.sys should manage that.
Oh, win32k, how we love you... so many vulnerabilities in just one little kernel-mode component!
GoodDayToDie said:
The purpose of this is to make it "safer" to jailbreak 8.1, since if you change the code integrity flag in 8.1 and leave it changed for any length of time, the system will crash due to PatchGuard. This driver is so you can only change the code integrity settings when you need to load unsigned code, giving minimal time for PatchGuard to notice and minimizing the risk of a crash.
HOWEVER, you cannot load this driver unless you already have unsigned code execution through some other means. That other means has not yet been published; if you want to use this tool you will need to figure out how to install it yourself (or wait for a published hack).
Click to expand...
Click to collapse
Does this work?
http://msdn.microsoft.com/en-us/library/ff547565.aspx
Hi Everybody!
There are lots of threads out there all asking about RT/2 images. (iso)
This does NOT apply to pro!
http://forum.xda-developers.com/showthread.php?t=2487580
http://forum.xda-developers.com/showthread.php?t=2215727
Let me clarify a few things:
Windows 8.0 RT works on both Surface RT and Surface 2
This means you can have Windows 8.0 RT on a Surface 2
The image I host only works on Surface RT's you need to patch your wim to work on Surface 2.
Now on to 8.1:
If you have a surface RT and you want 8.1, you should install the 8.0 image then upgrade to 8.1 via store.
If you have a surface RT and you want 8.1, and you have a 8.1 image, you should use it.
If you have a Surface 2 and you want 8.1 your Surface came preloaded with 8.1. However you can also download 8.1 images and install them.
How to dual boot?
If you own either surface you may want to dual boot 8.0 and 8.1. You cannot boot from SD CARD!
Follow this guide to dual boot both OSes. However in the guide it says 32gb tablets don't work. They do. I have my Surface RT 32gb tablet setup this way.
The reason to dual boot for me was so I could Run Jailbreak on 8.0 but have 8.1's features.
I have a modified version of the guide that I used that worked better for me.
Code:
1. manage-bde -protectors -disable c:
2. Shrink your OS partition from disk manager GUI leaving about 12 Gb free space.
3. Create new partition over the free space, format it to NTFS, add a drive letter, say, F:
4. Obtain image.wim from your image and then run powershell as an admin:
Dism /apply-image /imagefile:full-path-to-your-install.wim /index:1 /ApplyDir:F:\
5. Add the needed entries to boot-menu:
bcdedit /copy “{current}” /d "Windows RT 8.0”
bcdedit
look at bottom guid (identifier) and insert it between {}
bcdedit /set “{}” device partition=F:
bcdedit /set “{}” osdevice partition=F:
bcdedit /timeout 5
6. disable Bitlocker on the new partition (something like manage-bde -protectors -disable f:)
7. Reboot
Hope this helps!
If it did Hit the Thanks! button.
I host the Windows 8.0 RT image on my ftp server so if you want that PM me.
wcomhelp said:
Windows 8.0 RT image works on both Surface RT and Surface 2
This means you can have Windows 8.0 RT on a Surface 2
Click to expand...
Click to collapse
Is this true?? I've read at least one thread on this forum where somebody was working on trying to get RT 8.0 on a Surface 2 but I've yet to see it confirmed working.
Yes!
domboy said:
Is this true?? I've read at least one thread on this forum where somebody was working on trying to get RT 8.0 on a Surface 2 but I've yet to see it confirmed working.
Click to expand...
Click to collapse
The reason I wrote this guide was so people could see what they could do. I have tested it and it works just fine.
I have my Surface RT and Surface 2 both dual booting Windows RT 8.0 and Windows RT 8.1
wcomhelp said:
The reason I wrote this guide was so people could see what they could do. I have tested it and it works just fine.
I have me Surface RT and Surface 2 both dual booting Windows RT 8.0 and Windows RT 8.1
Click to expand...
Click to collapse
Very interesting! For the longest time Surface 2 owners wanting to jailbreak have been told they were just out of luck or to wait for the elusive 8.1 jailbreak. I guess now the answer is downgrade to RT 8.0.
domboy said:
Very interesting! For the longest time Surface 2 owners wanting to jailbreak have been told they were just out of luck or to wait for the elusive 8.1 jailbreak. I guess now the answer is downgrade to RT 8.0.
Click to expand...
Click to collapse
Yes this is the answer.
Trolling?
Oookiedo. .. I see here some methods of dual booting which is possible. However! I see that you need a 8.0 image to 'downgrade' 8.1 which will not work unless you started off at 8.0. Here in this guide it tells you how to dual boot and create your own image so when you do all those commands listed it's not actually downgrading your image or anything. If you use your own created image and follow this guide then congratulations you have dual booted 2 different versions of 8.1. So unless another person uploads 8.0 recovery then you are out of luck.
Would it be possible to boot from a USB device? (Surface 2)
**MIGHT be possible**
I have read a lot of blogs and forms here and from what I can tell it is not possible. There are a lot of forms where other developers are trying to break into 8.1 jailbreak. To think of it were that easy and downgrade they would have already released it as an official way of jail breaking the surface 2 rt. Though it could be one of those things where you are too close to a project to see the easy way out.
I have tried making a boot able USB stick with posted recoveries posted through out several different tech forms with no luck. All the surface 2 rt seems to do is crash instantly (and by crash I mean instant blue screen of death followed by extreme pixelized broken text and background almost unreadable) though the files are 3.4 gigs and it is very possible the files that I have gotten were corrupted. So I have not gotten the 8.0 image from someone posting the 8.0 image this year. If anybody happens to have a working surface rt with an 8.0 image and posts it I would be more then happy to give it a go.
Developguy said:
I have read a lot of blogs and forms here and from what I can tell it is not possible. There are a lot of forms where other developers are trying to break into 8.1 jailbreak. To think of it were that easy and downgrade they would have already released it as an official way of jail breaking the surface 2 rt. Though it could be one of those things where you are too close to a project to see the easy way out.
I have tried making a boot able USB stick with posted recoveries posted through out several different tech forms with no luck. All the surface 2 rt seems to do is crash instantly (and by crash I mean instant blue screen of death followed by extreme pixelized broken text and background almost unreadable) though the files are 3.4 gigs and it is very possible the files that I have gotten were corrupted. So I have not gotten the 8.0 image from someone posting the 8.0 image this year. If anybody happens to have a working surface rt with an 8.0 image and posts it I would be more then happy to give it a go.
Click to expand...
Click to collapse
i can confirm that yes it bluescreens in that coold pixely way(I have downloaded and tested the iso multiple times).
however that it even boots means something
Developguy said:
I have read a lot of blogs and forms here and from what I can tell it is not possible. There are a lot of forms where other developers are trying to break into 8.1 jailbreak. To think of it were that easy and downgrade they would have already released it as an official way of jail breaking the surface 2 rt. Though it could be one of those things where you are too close to a project to see the easy way out.
I have tried making a boot able USB stick with posted recoveries posted through out several different tech forms with no luck. All the surface 2 rt seems to do is crash instantly (and by crash I mean instant blue screen of death followed by extreme pixelized broken text and background almost unreadable) though the files are 3.4 gigs and it is very possible the files that I have gotten were corrupted. So I have not gotten the 8.0 image from someone posting the 8.0 image this year. If anybody happens to have a working surface rt with an 8.0 image and posts it I would be more then happy to give it a go.
Click to expand...
Click to collapse
Well, the OP said he hosts the RT 8.0 image and to PM him for it.
Honestly I still have my doubts about RT 8.0 on Surface 2, so I'd love to see if somebody can show it running as I've read some of the same threads you're probably referring to... and until this thread nobody had reported any success.
Thanks domboy for helping while I was away. You are correct I DO host the 8.0 images. I am running Windows 8.0 on my surface 2. Somewhere myrachan said something about the signatures being trusted...just do a search. The image I have is in .zip form so you can do whatever with it this includes both making a recovery usb as well as dualbooting.
8.0 Image
I have downloaded the 8.0 image the OP has hosted. I am going to see if the image he had posted is any different from what i have downloaded in the past. Wish me luck.
YEAAAH
Developguy said:
I have downloaded the 8.0 image the OP has hosted. I am going to see if the image he had posted is any different from what i have downloaded in the past. Wish me luck.
Click to expand...
Click to collapse
YEAAAAH It doesn't work. I've imported all the files and its a hard core blue screen. waaamp waaamp.
---------- Post added at 02:41 AM ---------- Previous post was at 02:21 AM ----------
Does this only work if you are dual booting? I did try just a straight recovery. Maybe the partition opened in the steps listed in the earlier is fine with the 8.0 installation. The issue may be Microsoft actually placing a block on the 8.1 install on the main partition namely 8.1. So it is possible to boot from usb to the new partition?
I don't think it will work...MS hasn't released signed drivers for Surface 2 for Windows 8.
wcomhelp > could you please post a video and/or images of a working 8.0 on your Surface 2
OP: More info
Windows RT 8.0 trusts surface 2 Drivers. You have to use dsim or dism whatever; you get the point. After deploying, NOT installing you need to run a tool called sysprep. after this you are done. the drivers should be included in your original .wim file. you cannot simply use a Surface RT image on the surface 2. I was incorrect about that. Sorry I forgot what I had to do to make it work. Working at university with kids who have had coop terms at MS helps a lot in projects like this. Since the Surface 2 was one of my friends and I no longer have it I cannot post a vid of ss right now. I tired so if this post is awful that's why.
What this means
filfat said:
i can confirm that yes it bluescreens in that coold pixely way(I have downloaded and tested the iso multiple times).
however that it even boots means something
Click to expand...
Click to collapse
The fact that it boots means the signatures are trusted...now all you need is a patched wim and you are good to go.
I don't understand.
Read this post
freeandroid4248 said:
I don't understand.
Click to expand...
Click to collapse
http://forums.mydigitallife.info/th...ing-about-Windows-RT-(WOA)-v8-x-x-and-v10-ARM
He tells you how to merge the oem drivers with yours. Follow the forum rules I binged.it so could have you. This guy did the exact same thing I did.
wcomhelp said:
http://forums.mydigitallife.info/th...ing-about-Windows-RT-(WOA)-v8-x-x-and-v10-ARM
He tells you how to merge the oem drivers with yours. Follow the forum rules I binged.it so could have you. This guy did the exact same thing I did.
Click to expand...
Click to collapse
Ya I know that post, in fact I posted on the first page of it (jon5798) . Read the last page of that post please.....I asked Moderate last night...he says its not possible unless Microsoft releases signed Windows 8.0 drivers...I tend to believe him because he knows a lot more about Windows RT than us.
First i happy that you can get windows rt 8 and 8.1 withdualboot
but i make some test that for shrink the size for partation of windows to get at least 12 gb
it was impossible to doing that in surface 2
becouse the windows allow you to shrink size with 5 gb at least
i know that it hard to belive but you can try that with surfae 2
i know there space not used as 18 gb
but that happen with me .
is there any solution for that to make new partation as 12-16 gb
Thank you
Hello.
Microsoft is working on an ARM version of Windows 10. It is already possible to get this working on a Raspberry PI 2.
According to this article:
https://www.modmy.com/developers-successfully-run-windows-10-surface-rt
someobdy managed to get Windows 10 partially working on a Surface RT. Is there any update on this? Considering Microsoft has an ARM version of Windows 10, what are the issues in getting this working?
kephax said:
Hello.
Microsoft is working on an ARM version of Windows 10. It is already possible to get this working on a Raspberry PI 2.
According to this article:
https://www.modmy.com/developers-successfully-run-windows-10-surface-rt
someobdy managed to get Windows 10 partially working on a Surface RT. Is there any update on this? Considering Microsoft has an ARM version of Windows 10, what are the issues in getting this working?
Click to expand...
Click to collapse
Windows 10 on ARM is exclusively for ARM64 devices. The version that runs on the raspberry pi 2 is Windows 10 IoT. Win10 iot can run on the surface tablet, but due to lack of apps, it is practically useless.
There is any news about win10 on arm on Surface rt ?
Lord-THX said:
There is any news about win10 on arm on Surface rt ?
Click to expand...
Click to collapse
No
Thanks
https://m.ithome.com/html/469731.htm
Here ^^^^
wangxiaohu said:
Here ^^^^
Click to expand...
Click to collapse
Does that really work on a Surface 2? I could never get nvpep to work, it would always cause a bluescreen on boot (irql_not_less_or_equal).
I can't download your Surface 2 English WIM from that site, can you tell me if there is there a mirror? Failing that a tip on how you got nvpep working would be interesting
Thanks!
wangxiaohu,
I managed to get your Surface 2 WIM, works great aside from the expected Bluetooth issue. Use the Uart16550tegra driver from Surface RT on Surface 2, once this is installed the Bluetooth will work.
Thanks to Ranomez for the tip
_CNR_ said:
Does that really work on a Surface 2? I could never get nvpep to work, it would always cause a bluescreen on boot (irql_not_less_or_equal).
Click to expand...
Click to collapse
Just spotted where I went wrong. I've been using sdbus.sys and sdstor.sys from a factory Surface 2 RT8.1 install, using these got me to desktop but I could never get nvpep to work without a BSOD on boot. Just noticed the sdbus.sys from the Chinese WIM is older than the one I took from my Surface 2 RT8.1 install.
sdbus 9.3.9600.16497 bad, 9.3.9600.16384 good. Combo of any nvpep and sdbus 9.3.9600.16497 under 15035 will break it.
wangxiaohu said:
https://m.ithome.com/html/469731.htm
Here ^^^^
Click to expand...
Click to collapse
Wait what?!? Is this the real Windows 10 ARM Edition running on a Surface RT/2? Not IoT? If so, where did this come from? I thought Windows 10 ARM Edition was ARM64 not ARM32. I can kind of follow it, but relying on browser translation of the page...
domboy said:
Wait what?!? Is this the real Windows 10 ARM Edition running on a Surface RT/2? Not IoT? If so, where did this come from? I thought Windows 10 ARM Edition was ARM64 not ARM32. I can kind of follow it, but relying on browser translation of the page...
Click to expand...
Click to collapse
Yes. But it's also last build that can run ARM32. We won't see newer version of Windows 10 on rt most likely.
domboy said:
Wait what?!? Is this the real Windows 10 ARM Edition running on a Surface RT/2? Not IoT? If so, where did this come from? I thought Windows 10 ARM Edition was ARM64 not ARM32. I can kind of follow it, but relying on browser translation of the page...
Click to expand...
Click to collapse
_CNR_ said:
Does that really work on a Surface 2? I could never get nvpep to work, it would always cause a bluescreen on boot (irql_not_less_or_equal).
I can't download your Surface 2 English WIM from that site, can you tell me if there is there a mirror? Failing that a tip on how you got nvpep working would be interesting
Thanks!
Click to expand...
Click to collapse
Yes it works... There are some caveats not stated in the instruction.
wangxiaohu said:
Yes. But it's also last build that can run ARM32. We won't see newer version of Windows 10 on rt most likely.
Click to expand...
Click to collapse
That's really cool! I had no idea there was a build of Windows 10 ARM Edition that would run on the Surface RT/2. Thanks for posting the link to those instructions!
I suspect you're correct about no newer builds. Though considering my old Surface RT is still running RT 8.0 for the jailbreak, any version of 10 would be a lot newer. Am I correct in assuming all the open-source apps compiled for RT (since they're ARM32) would also run on this build of Windows 10? I'm going to have to try this when I get some time.
domboy said:
That's really cool! I had no idea there was a build of Windows 10 ARM Edition that would run on the Surface RT/2. Thanks for posting the link to those instructions!
I suspect you're correct about no newer builds. Though considering my old Surface RT is still running RT 8.0 for the jailbreak, any version of 10 would be a lot newer. Am I correct in assuming all the open-source apps compiled for RT (since they're ARM32) would also run on this build of Windows 10? I'm going to have to try this when I get some time.
Click to expand...
Click to collapse
I want to set expectation clear that I still find rt with Windows 10 useless since it's doesn't have any perf improvement. Experience is awful. Camera doesn't work. Photo and Mail apps don't install. Edge browsing is more compatible with sites than IE, but extremely slow.... So, don't bother unless u want to enjoy the 'upgrade' per se.
wangxiaohu said:
I want to set expectation clear that I still find rt with Windows 10 useless since it's doesn't have any perf improvement. Experience is awful. Camera doesn't work. Photo and Mail apps don't install. Edge browsing is more compatible with sites than IE, but extremely slow.... So, don't bother unless u want to enjoy the 'upgrade' per se.
Click to expand...
Click to collapse
I appreciate the warning! I am not surprised to hear that it is slow, otherwise Microsoft might have actually released it officially. I probably will wait to try this until I have no other use for the device (once the Netflix app stops working). Still, it's neat to see it is actually possible.
wangxiaohu said:
Yes. But it's also last build that can run ARM32. We won't see newer version of Windows 10 on rt most likely.
Click to expand...
Click to collapse
There are apparently newer ARM32 builds but its very unlikely we will ever get to see them and as it stands I think we are lucky to have 15035.
wangxiaohu said:
I want to set expectation clear that I still find rt with Windows 10 useless since it's doesn't have any perf improvement. Experience is awful. Camera doesn't work. Photo and Mail apps don't install. Edge browsing is more compatible with sites than IE, but extremely slow.... So, don't bother unless u want to enjoy the 'upgrade' per se.
Click to expand...
Click to collapse
My nvpep troubles:
I found where I was going wrong with my WIM (thanks to your WIM) and what was causing nvpep to trigger a BSOD on boot. I don't understand the underlying cause but I was using sdbus 9.3.9600.16497 from my Surface 2 RT8.1 install (Surface2_BMR_20.2.19.0 recovery media), once I switched to sdbus 9.3.9600.16384 everything was fine.
Once that was sorted I was able to make my own working WIM and I've been playing with making it work as well as possible on my Surface 2:
Error on first boot:
Before allowing 15035 to boot for the first time create a new directory (\EFI\Microsoft\Recovery) and create an empty BCD store there.
Camera fix:
Code:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Media Foundation\Platform]
"EnableFrameServerMode"=dword:00000000
Bluetooth fix:
Use the Uart16550tegra driver from Surface RT on Surface 2, once this is installed the Bluetooth will work.
Edge Tweaking:
Edge can be made a little better from about:flags - enable canary and allow high memory usage. This is not my tip but it seems to help, only real issue I have with Edge at the moment is YouTube but I've been told to give myTube a try.
Build Expired Nag Window:
Delete File \Windows\System32\LicensingUI.exe
Apps Working:
So far managed to get working the following MS apps: Onedrive, Remote Desktop, Skype, Photos, Camera, Scan, Films & TV, Mail & Calendar. Oh, and also an old version of Maps that still works - GPS is good. Third party apps tried so far - Team Viewer & VLC.
Pictures: https://imgur.com/a/ujnLlFI
List of apps that that seem to work on Windows 10 15035 so far - newer versions may work but would require manifest mods:
Code:
Microsoft.DesktopAppInstaller_2019.1019.1.0_neutral_~_8wekyb3d8bbwe
Microsoft.WindowsStore_11811.1001.2713.0_neutral_~_8wekyb3d8bbwe
Microsoft.MicrosoftSkyDrive_17.30.3.0_neutral_~_8wekyb3d8bbwe
Microsoft.RemoteDesktop_10.1.1107.0_neutral_~_8wekyb3d8bbwe
Microsoft.SkypeApp_12.1815.210.1000_neutral_~_kzf8qxf38zg5c
Microsoft.Windows.Photos_2017.35063.44410.1000_neutral_~_8wekyb3d8bbwe
Microsoft.WindowsCamera_2017.727.40.2000_neutral_~_8wekyb3d8bbwe
Microsoft.WindowsScan_2014.523.326.3026_neutral_~_8wekyb3d8bbwe
Microsoft.ZuneVideo_2019.18052.10711.0_neutral_~_8wekyb3d8bbwe
Microsoft.WindowsCommunicationsApps_16005.11001.20116.0_neutral_~_8wekyb3d8bbwe.appxbundle
Microsoft.WindowsMaps_4.1509.50912.0
TeamViewer.31414B719FA93_15.0.100.0_neutral_~_89446h4zmeyyt
VideoLAN.VLC_3.2.1.0_neutral_~_paz6r1rewnh0a
Not exactly current in some cases but they still seem to function.
These I have installed but not used. It would be a surprise if the wireless display worked (I don't have the adapter) and I'm not a telegram user but will sign up to test later.
Code:
Microsoft.SurfaceWirelessDisplayAdapter_3.4.137.1000_neutral_~_8wekyb3d8bbwe
38833FF26BA1D.UnigramPreview_3.6.2286.0_neutral_~_g9c9v27vpyspw
I'm not really a big app user so I've just been adding stuff to make 15035 feel a little less empty
There is this version of Maps:
Code:
Microsoft.WindowsMaps_2017.1003.1829.0_neutral
Should work on 15035 but it requires 15063 as a minimum to install and I have not looked into what's required to modify the manifest, repack and sign yet. For the moment I've focused on what will work without too much trouble.
Qiangong2 said:
No
Click to expand...
Click to collapse
@Qiangong2
Are you going to try this? Need your feedback.
k4955 said:
@Qiangong2
Are you going to try this? Need your feedback.
Click to expand...
Click to collapse
I tried but the install was so glitchy that I reverted back to RT 8.1.
Qiangong2 said:
I tried but the install was so glitchy that I reverted back to RT 8.1.
Click to expand...
Click to collapse
Once installed its not bad, I've got a dual boot setup on my Surface 2 just to be on the safe side though.
Hi everybody.
Here is the story of the pointless week I just had. Some of the information might be needed to help me, but if you want you can skip to the end for the actual question.
I got hold of an old surface rt at my girlfriend's place and, since I left my laptop in my own house, I thought I might try to set it up and use it for a few things I needed to do (not much more than checking emails, watching youtube and stuff like that). I quickly realised the device was a bit useless (microsoft store and windows update were not working properly, internet explorer being internet explorer and so on).
I then found a guide from alexenferman, and a few threads in this forum, on how to install windows 10. I am neither developer nor a true geek, but I can follow instructions and I messed about with this type of things in the past, so I thought I'd give it a try.
The first half of the process went quite smoothly and I was able to install windows 10 with SecureBooth disabled. The only issues I had were that I could not update windows 10 either, and I could not sign in with a microsoft account, which prevented me to use the store again and I had no way of installing apps from the appstore put together by alexenferman.
Quite frankly, I just got tired of wasting my time, so I decided to revert back to 8.1. For that, I first clean installed windows 8. Then, since I could not update to 8.1, I used a usb recovery image and reset my surface rt with windows 8.1.
At the moment I am on windows 8.1, the store works, but windows update doesn't. I keep checking for updates and get different errors. After troubleshooting a couple of times I now just get error 8024A000. I looked it up and tried the methods found online, sfc scannow cannot find anything, other fixes do not really work. Basically I feel in a loop and a bit lost (Speaking of loops, contacting microsoft support has been an infinite loop between the windows and surface division).
tldr: is there anybody here that can help me with updating Windows 8.1 RT (My goal would be to get to update 3 and possibly jailbreaking after that)? Did I mess things up irreversibly by installing windows 10? Should I just buy a new tablet and chuck away this useless piece of junk that is causing me a nervous breakdown? Thank you very much for your attention, and sorry for the lengthy message but I need someone to talk to, somebody that doesn't simply repeat a script.
Updates ( read: patches ) automatically get rolled out by OEM if they deem it necessary.