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
Related
----
Thanx for your hard work jon4248 I'm hoping this will fix my non responsive touch screen......and a torrent link would be awesome to help my low bandwidth and constant drop outs.
angusc said:
Thanx for your hard work jon4248 I'm hoping this will fix my non responsive touch screen......and a torrent link would be awesome to help my low bandwidth and constant drop outs.
Click to expand...
Click to collapse
I've had reports from other people that it doesn't resolve that issue. I've never had that issue, but I've read that the only way to fix is to completely drain the surface 2 battery, until nothing comes in the screen and let it sit for a while, then fully charge it.
torrent attached, I maybe the only seed but I have fibre so it should be fast.
Thanx man!
I managed to download the file and flashed it successfully to my surface. As you said above, it did NOT fix my touch screen issues
I will try the drain battery totally and see what happens. I will report back if any success.
Thanx again for your work.
No success with battery draining.....I read other forum and Windows support page suggesting it's a known issue due to software updates and a fix will be release but don't know when.....very annoying as a tablet without touch is like a chocolate fire guard......totally useless!
EDIT: after a recent update I got touch screen function back again! Now I switched off further updates.
Added "update 3"
Updated to today. Enjoy!
Jon4248 said:
Updated to today. Enjoy!
Click to expand...
Click to collapse
If it's okay with you Jon4248, I Integrated some drivers from the original surface pro with your zip I can upload a copy here when I work out the kinks.
If any one has the new driver and firmware set for the original surface could you give me the link? If not i'm pretty sure I have them around here somewhere.
The wim file won't work on Surface pro, as it's Windows RT. You’ll have to build one from scratch using sysprep.
Jon4248 said:
The wim file won't work on Surface pro, as it's Windows RT. You’ll have to build one from scratch using sysprep.
Click to expand...
Click to collapse
I Haven't got around to using sysprep yet, but I managed to install a Frankenstein version of sorts made out of a bunch of different builds of RT I procured. There is no EFI or Boot directories on the main windows partition, but I far as I can tell Secure Boot is still enabled, also I could of Swore I also had a MBR partition but now it's showing as GPT since I let windows update, but that could of just been disk management acting up.
Any idea if this is any use to the community? if you want I could post some screens. Also I installed windows by booting to the recovery flash drive starting dos then running diskpart. Under diskpart I then procedded to clean the main disk- Scary, huh?. Next I went and ran setup.exe in the resources directory so it might install more like a build of windows on a x86 platform.
It is here,
https://dl.winehq.org/wine-builds/android/
But ain't working on pixel. I am pissed off. Any workarounds?
It is not compatible with Oreo yet.
Just let them know on their forums:
https://forum.winehq.org/viewforum.php?f=2
NoobInToto said:
It is here,
https://dl.winehq.org/wine-builds/android/
But ain't working on pixel. I am pissed off. Any workarounds?
Click to expand...
Click to collapse
Look into Crossover. It uses WINE. http://www.androidpolice.com/2017/11/07/crossover-android-chrome-os-enters-open-beta/
skawtnyc said:
Look into Crossover. It uses WINE. http://www.androidpolice.com/2017/11/07/crossover-android-chrome-os-enters-open-beta/
Click to expand...
Click to collapse
Unfortunately, it is not for ARM devices...
I hope they'll update it so it's compatible with Android Oreo devices.
Looks like the new WIne 3.0 is ARM-compatible, and has been compiled for ARM devices:
https://dl.winehq.org/wine-builds/android/
I have Oreo on my Nexus 7 2013, wine works, tried to install some apps but no luck, only errors. Internet Explorer works, but i see only blank white web pages
numbazZ said:
I have Oreo on my Nexus 7 2013, wine works, tried to install some apps but no luck, only errors. Internet Explorer works, but i see only blank white web pages
Click to expand...
Click to collapse
what kind if binaries / apps were u trying to run?
nine7nine said:
what kind if binaries / apps were u trying to run?
Click to expand...
Click to collapse
Tried Live For Speed installer, also exe from unpacked game, and some photoshop cs6 repack) as i know LFS works good on wine.
Will try something else tomorrow
numbazZ said:
Tried Live For Speed installer, also exe from unpacked game, and some photoshop cs6 repack) will try something else tomorrow
Click to expand...
Click to collapse
how about trying actual arm binaries?
ie; windows rt, win8 arm && win10 arm PEs
last I heard, while the wine devs are working on x86 on arm, it wasn't ready - when compared to say; win10 for arm's x86 emulation layer...
I also know that in the past to run x86 binaries in wine on arm, you have to have binfmt_misc enabled in the kernel + qemu (emulator) to make it all work...
not sure, where things are at, at the moment. but I'd try running actual Arm compiled windows app and see if they run.... idk, I can't imagine that Wine is super useful on android yet. that said, I am curious - as I used to maintain buillds and patchsets for wine...
Only binaries compiled for ARM will function under Wine. You can find an updated list in the second post of this thread: https://forum.xda-developers.com/showthread.php?t=2092348
skawtnyc said:
Only binaries compiled for ARM will function under Wine. You can find an updated list in the second post of this thread: https://forum.xda-developers.com/showthread.php?t=2092348
Click to expand...
Click to collapse
it should be noted, this is specifically windows rt / win8 arm apps... and hasn't been updated in 3yrs.
I suspect that if u were to investigate the windows app store / UWP apps - there are probably a much higher number of windows apps that potentially could run in wine / for arm - but then you would likely require the Microsoft store or some other way to get the apps running in wine (not sure if wine even supports them).
skawtnyc said:
Looks like the new WIne 3.0 is ARM-compatible, and has been compiled for ARM devices:
https://dl.winehq.org/wine-builds/android/
Click to expand...
Click to collapse
It is not pixel compatible, and that is all this thread is about.
NoobInToto said:
It is not pixel compatible, and that is all this thread is about.
Click to expand...
Click to collapse
To be honest I only installed it on my Pixel C, not my Pixel phone. Doing so would have been pointless since the resolution makes it very difficult to use. Also there's no way to access the software keyboard, making it even more difficult to use.
Even if you could install it, and those other issues were resolved, it doesn't have a x86 emulation layer so you're pretty much stuck with those old Windows RT apps and not much else. You're looking at something that really doesnt have much more value than proof of concept. I'm probably going to end up migrating my tablet to something like the Pixelbook so I can run Crossover on it and have both android and x86 Windows apps run natively.
skawtnyc said:
To be honest I only installed it on my Pixel C, not my Pixel phone. Doing so would have been pointless since the resolution makes it very difficult to use. Also there's no way to access the software keyboard, making it even more difficult to use.
Even if you could install it, and those other issues were resolved, it doesn't have a x86 emulation layer so you're pretty much stuck with those old Windows RT apps and not much else. You're looking at something that really doesnt have much more value than proof of concept. I'm probably going to end up migrating my tablet to something like the Pixelbook so I can run Crossover on it and have both android and x86 Windows apps run natively.
Click to expand...
Click to collapse
Well, I would still like to try it out. If they manage to make it work with windows 10, say, windows 10S , it would be cool, since windows 10 is more touch friendly than 7 . It is in the works I believe, to be made possible via qemu (full arm compatibility). Time will tell.
NoobInToto said:
It is not pixel compatible, and that is all this thread is about.
Click to expand...
Click to collapse
NoobInToto said:
Well, I would still like to try it out. If they manage to make it work with windows 10, say, windows 10S , it would be cool, since windows 10 is more touch friendly than 7 . It is in the works I believe, to be made possible via qemu (full arm compatibility). Time will tell.
Click to expand...
Click to collapse
My biggest regret about this is that I don't have an emulator to run Diablo II on my tablet. Sure, there are other games, but they don't really capture the experience the same way.
skawtnyc said:
My biggest regret about this is that I don't have an emulator to run Diablo II on my tablet. Sure, there are other games, but they don't really capture the experience the same way.
Click to expand...
Click to collapse
I managed to make doom 3 to work on my phone ( I don't recollect which one, pixel or nexus 6p, I switched to pixel about 2 months ago). I am not sure about diablo.
NoobInToto said:
It is not pixel compatible, and that is all this thread is about.
Click to expand...
Click to collapse
beyond installing, it doesn't seem to work for me... also, i'm unclear on whether this build is arm64 compatible.? (I know wine has an arm64 preloader though).
skawtnyc said:
Even if you could install it, and those other issues were resolved, it doesn't have a x86 emulation layer so you're pretty much stuck with those old Windows RT apps and not much else. You're looking at something that really doesnt have much more value than proof of concept. I'm probably going to end up migrating my tablet to something like the Pixelbook so I can run Crossover on it and have both android and x86 Windows apps run natively.
Click to expand...
Click to collapse
I suspect that running qemu + wine-x86 would be the better route to go (vs wine-arm or running qemu + windows)... i'm not too sure what the overhead would look like, but people are doing it on the rasberry pi 2/3...
it's probably also possible that using some of wine's env variables would improve performance (realtime priviledges for wineserver, critical threads, etc) and patching wine to support other enhancements (which is what I would do anyway, on my linux box).
NoobInToto said:
Well, I would still like to try it out. If they manage to make it work with windows 10, say, windows 10S , it would be cool, since windows 10 is more touch friendly than 7 . It is in the works I believe, to be made possible via qemu (full arm compatibility). Time will tell.
Click to expand...
Click to collapse
i'd like to, as well...
technically, you can run qemu + x86 wine on arm, right now. I just don't believe that anyone has packaged it up nicely for android...
and it would require additional manual configuration, init script, possibly a script/wrapper for launching apps too, depending... Another issue would be the vast majority of stock kernels don't have the support or enable stuff that is going to be required... mine suports binfmt_misc (which qemu will require), but i think other stuff may be needed. not positive.
it can't be that hard though, but I don't have much experience with qemu (and none on android), wine on the other hand - lots of experience with on linux. same goes for winelib...
does anyone know how to get access to the internal storage?
I cant even try to install anything, because I dont know where the Wine-Files are located.
Btw I'm using a Lenovo YogaBook
Thanks
trfr3ak said:
does anyone know how to get access to the internal storage?
I cant even try to install anything, because I dont know where the Wine-Files are located.
Btw I'm using a Lenovo YogaBook
Thanks
Click to expand...
Click to collapse
you'll have to figure out how to get into your internal storage yourself, but having a a proper file manager helps. you may need root to view the files (I did on my pixel)... also, not sure why you are asking for help for your yogabook in the google pixel forum...? (you probably shouldn't be).
as for where the files are. it's android, so app data is usually stored in /data/data/your.app.name... and this would be where wine installs it's binaries and prefix too. (org.winehq.wine)
---------- Post added at 10:22 PM ---------- Previous post was at 10:18 PM ----------
so yeah. looking at the binaries. they are compiled as arm-v7a. ... they should run (although, by default after install, they aren't in the PATH / can't be executed from a terminal)....
I guess maybe the arm64 version just isn't ready at this point && wine-3.0 for arm requires some manual setup on the pixel... might tinker with it later, or look into qemu + wine x86... we'll see
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.
Hey all, it's probably been a while since I posted, but as time has went on, I've been working on Otter Browser ports.
It isn't stable, which is why it says BETA! Please say if something isn't working, I'll look at it when I can.
What can it do so far?
Some sites are more faster than Edge
What can it not do?
Large JavaScript sites/files. Multimedia was fixed(-ish) (some formats do not work, will look into it soon, could just be a Qt thing)!
How stable exactly is "not stable"?
Well, it crashes at random. If you go to a site with too much JavaScript it will crash, certain sites just don't work, etc.
Will this all be fixed!
Of course! I'm working on it as much as I can!
If you want to test it out, let me know how it works, etc, then that would be gladly appreciated, I'm trying to do what I can for the peeps only with an ARM32 device.
Tested sites: https://docs.google.com/spreadsheets/d/14lQLsQoMKNPalPbF7SQLxCgpOp80a82vM9aeRV6xOd0/edit?usp=sharing
Download link(s):
Latest (permalink)
https://download.pahaze.net/ARM/Applications/OtterBrowser/Downloads/latest/
Archive of versions
https://download.pahaze.net/ARM/Applications/OtterBrowser/Downloads/
10/10/2021 build - EARLY WebKit2/WebGL/OpenGL build - NO YouTube/JIT still
7z - https://drive.google.com/file/d/1qksSsGFAY2-7qcJe_ezG0R4YZRSmqRzJ/view?usp=sharing
ZIP - https://drive.google.com/file/d/1diTYLr0Cwm5L0944rjJfSedjUqTN97HT/view?usp=sharing
7/29/2021 build - EARLY MULTIMEDIA BUILD - NO YouTube YET
https://drive.google.com/file/d/1TXKqeMRkWY7Y_ejDTXoj-Qs3Fma43amG/view
4/22/2021 build
https://drive.google.com/file/d/1UvpJJuombejj_hh15sIyHA-_d2Y_flQZ/view?usp=sharing
How do I install it!!!
Extract the folder from the 7zip file ANYWHERE. It doesn't matter where it is!
C:\Program Files; your desktop; you name it, it'll work just fine there. I do plan on making an installer, but for the time being, a folder on your desktop or in your documents or something isn't going to hurt.
Have fun out there!
Thanks for that, hope some people will give you feedbacks. I'm so pissed at Microsoft for letting this perfectly working tablet die.
keepah said:
Thanks for that, hope some people will give you feedbacks. I'm so pissed at Microsoft for letting this perfectly working tablet die.
Click to expand...
Click to collapse
My pleasure! I'm going to update it as much as possible, but I'm still in school so updates won't be immediate or frequent compared to the official Otter builds. I love the lil tablets myself and had been using my Surface 2 as a main PC until early 2020.
Hi. I'm trying to run it on a Nokia Lumia 2520 (it runs Windows RT 8.1) and has A ARM32 hardware. I tried to use Otter but windows just gives me an error message saying that it cannot verify the digital signature for this file. Is there a workaround to this?
Traceur_M said:
Hi. I'm trying to run it on a Nokia Lumia 2520 (it runs Windows RT 8.1) and has A ARM32 hardware. I tried to use Otter but windows just gives me an error message saying that it cannot verify the digital signature for this file. Is there a workaround to this?
Click to expand...
Click to collapse
Sounds like you still need "jailbreak" it for this browser to run. There are threads in the RT subform on how to do that. I never upgraded to 8.1 so I haven't tried that procedure myself...
Traceur_M said:
Hi. I'm trying to run it on a Nokia Lumia 2520 (it runs Windows RT 8.1) and has A ARM32 hardware. I tried to use Otter but windows just gives me an error message saying that it cannot verify the digital signature for this file. Is there a workaround to this?
Click to expand...
Click to collapse
Yeah, you just need to sign it with a signtool. The one in the forums here works. Just be sure RT8.1 has the jailbroke ran. It runs worse on RT8.1, from what I've heard though (just warning). You may also need to put these DLLs in it's folder.
Hello , I have tested your browser on Lumia 930 running a leaked version of Windows Arm 32.
It's UI and some pages work flawlesslly but it warns about SSL not being supported or something like that.
Do you maybe have a telegram account? You would surelly be welcomed on WOAaarch32 telegram group
Horuhe Delaroddia said:
Hello , I have tested your browser on Lumia 930 running a leaked version of Windows Arm 32.
It's UI and some pages work flawlesslly but it warns about SSL not being supported or something like that.
Do you maybe have a telegram account? You would surelly be welcomed on WOAaarch32 telegram group
Click to expand...
Click to collapse
I'm glad to hear that it's working good, but that SSL is a little mistake by me... I forgot to copy and rename some DLLs. I'll fix it in a future build, sorry about that. It's nothing bad, just a DLL spelling mistake.
Also, sadly, no, I do not have Telegram. I would like to get it but as I'm a minor I can not easily get whatever social media I please. If I do get it, I'll be sure to post it here.
frylockk19 said:
I'm glad to hear that it's working good, but that SSL is a little mistake by me... I forgot to copy and rename some DLLs. I'll fix it in a future build, sorry about that. It's nothing bad, just a DLL spelling mistake.
Also, sadly, no, I do not have Telegram. I would like to get it but as I'm a minor I can not easily get whatever social media I please. If I do get it, I'll be sure to post it here.
Click to expand...
Click to collapse
@Horuhe Delaroddia got it : )
I'm @frylockk19 on there and I already joined the Windows Aarch32 Lumia group
This is awesome, didn't think anyone was still working on apps for RT. So far so good way better than the ancient IE11 that 8.1 has.
aq3e said:
This is awesome, didn't think anyone was still working on apps for RT. So far so good way better than the ancient IE11 that 8.1 has.
Click to expand...
Click to collapse
Thanks! Glad you're enjoying it.
Just wanted to pop in and say that I tested this on the Windows 10 Build and it works just as well on my RT1 as it did on 8.1, Buggy but still as good as edge.
aq3e said:
Just wanted to pop in and say that I tested this on the Windows 10 Build and it works just as well on my RT1 as it did on 8.1, Buggy but still as good as edge.
Click to expand...
Click to collapse
That's awesome! RT8.1 isn't expected to do well with it though, sadly.. This is due to the whole THUMB2 limitations and junk . I plan on making stable RT8.1 releases and RT10 releases where the RT10 releases have JIT. Glad to hear how it's as good as Edge though. I'm doing what I can and hopefully will release a new/more stable build soon. I'm dealing with some issues (irl, not computer or whatnot), but hopefully should be back to building apps in a few days or so. Have fun with it!
It works!!!!
I will find you!
And i will kiss you!
Hello, I wanted to thank you for working on this Browser, it works on my Lenovo IdeaPad Yoga 11 which runs Windows 8.1 RT. I'm also wanted to report some bugs since on 8.1 there are some and I've seen anybody talking about them here. So here they are :
-1: When trying to erase (backspace) on a search engine page the browser will crash.
-2: When trying to access any website that allows you to sign in (ex: YouTube, any hospital or bank website) it crashes.
I'll stop at these two since, again, I'm not sure if it's the right place and I don't want to pollute the thread. If it's not the right place, I'll gladly report them wherever it is. So thank you in advance.
OlirexGamer said:
Hello, I wanted to thank you for working on this Browser, it works on my Lenovo IdeaPad Yoga 11 which runs Windows 8.1 RT. I'm also wanted to report some bugs since on 8.1 there are some and I've seen anybody talking about them here. So here they are :
-1: When trying to erase (backspace) on a search engine page the browser will crash.
-2: When trying to access any website that allows you to sign in (ex: YouTube, any hospital or bank website) it crashes.
I'll stop at these two since, again, I'm not sure if it's the right place and I don't want to pollute the thread. If it's not the right place, I'll gladly report them wherever it is. So thank you in advance.
Click to expand...
Click to collapse
You're absolutely fine reporting any issues here! I know about them, and I'm doing what I can but progress is slow due to stuff happening outside of porting and I only have so much RAM (8GB) so I only can build with like 6 jobs at a time ; )
The goal is to get Otter as close to Win32's version, but I may *drop* Otter if I can get GTK building as it seems to be more lightweight (an example being Midori). YouTube won't work at all though, for sure. No multimedia works, sadly. I don't know about banking/hospital site's logins as I'm a minor and do not have any accounts for any of them (lol), but I'll see if it's happening with stuff like GitHub and report back if I can fix it, or if there's a new build you can try out.
frylockk19 said:
You're absolutely fine reporting any issues here! I know about them, and I'm doing what I can but progress is slow due to stuff happening outside of porting and I only have so much RAM (8GB) so I only can build with like 6 jobs at a time ; )
The goal is to get Otter as close to Win32's version, but I may *drop* Otter if I can get GTK building as it seems to be more lightweight (an example being Midori). YouTube won't work at all though, for sure. No multimedia works, sadly. I don't know about banking/hospital site's logins as I'm a minor and do not have any accounts for any of them (lol), but I'll see if it's happening with stuff like GitHub and report back if I can fix it, or if there's a new build you can try out.
Click to expand...
Click to collapse
Okay, that's good to know. What I've seen is that it should crash with any page in which you have to log in for anything so, for example, I think this website would do the same or Gmail. Thank you for your work, we'll be waiting patiently for the next update.
OlirexGamer said:
Okay, that's good to know. What I've seen is that it should crash with any page in which you have to log in for anything so, for example, I think this website would do the same or Gmail. Thank you for your work, we'll be waiting patiently for the next update.
Click to expand...
Click to collapse
No problem!
Just want to tell you, that i am so thankfull for your work an the browser. The Surface is running so good and is doing such a good job for me. I cannot understand why MS let this Tablet die.
Only problem is, you know that, the Browser. Since the Win 10 Setup, the Edge Browser works "ok", but i have reached its limits very early.
Thank you again for your work, your afford and i hope you will continue with this browser.
Doc_Presley said:
Just want to tell you, that i am so thankfull for your work an the browser. The Surface is running so good and is doing such a good job for me. I cannot understand why MS let this Tablet die.
Only problem is, you know that, the Browser. Since the Win 10 Setup, the Edge Browser works "ok", but i have reached its limits very early.
Thank you again for your work, your afford and i hope you will continue with this browser.
Click to expand...
Click to collapse
No problem! I plan on continuing as much as I can with it and hoping next build I can get a JIT build out for the Win10 users even! Qt is just painfully slow to compile on my computer due to low RAM amount (8GB 2666MHz with a Ryzen 5) . May try to get a server or something to speed up builds.
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.