Related
Hello !
Curruntly winehq can run widows rt/ce apps on my Galaxy S Duos !
How to do it:
1)Flash a faster rom(like pmp (thx mohitash))
2)Download a compatible fedora armv7 img
3)Chroot into it
4)After chrooting:
[[email protected] /]:adduser rootCoder --force-badname (it's just an example) && su - rootCoder
[[email protected] /]:yum update && yum install wine
5)open androidVNC and then login to your vnc
6)open wine config
7)add all the possible libraries and apply them
8)set windows version to 8
9)open a ported windows rt/ce app via wine
10)EnJoY !
Don't forget to press Thx
You havent tried this yourself have you.... Either that or you havent clarified what apps you can and cannot run properly.
WINE does not support winrt at all. Only win32.
WINE does however support win32 on THUMB2 now and the wine wiki even directs you to GoodDayToDie's ported application thread. WINE can run these programs now.
It can do the ported desktop apps. It can't do store apps.
There is also a QEMU patch to allow x86 software to run under WINE on ARM, but its meant to be buggy at best and performance is terrible (although I wonder how it compares to maimachs little x86 emulator).
SixSixSevenSeven said:
You havent tried this yourself have you.... Either that or you havent clarified what apps you can and cannot run properly.
WINE does not support winrt at all. Only win32.
WINE does however support win32 on THUMB2 now and the wine wiki even directs you to GoodDayToDie's ported application thread. WINE can run these programs now.
It can do the ported desktop apps. It can't do store apps.
There is also a QEMU patch to allow x86 software to run under WINE on ARM, but its meant to be buggy at best and performance is terrible (although I wonder how it compares to maimachs little x86 emulator).
Click to expand...
Click to collapse
Sorry sir...you didn't understood what i mean
1)i had tried it and it's working for me
2)i said that ONLY windows rt apps(x86 apps cannot)
Sorry agin:angel:
curruntly tested apps by me :
-bochsx86emu
-prboom
-quake
-A process manager
.rootCoder. said:
Sorry sir...you didn't understood what i mean
1)i had tried it and it's working for me
2)i said that ONLY windows rt apps(x86 apps cannot)
Sorry agin:angel:
Click to expand...
Click to collapse
You still havent specified the difference between win32 and winrt apps (desktop and store).
Specifically WINE via this method will run the win32 applications from GoodDayToDies thread not apps from the windows store.
SixSixSevenSeven said:
You still havent specified the difference between win32 and winrt apps (desktop and store).
Click to expand...
Click to collapse
Differce is that apps are ported to arm that our device is running it(you need to jailbreak your device to run them)
.rootCoder. said:
Differce is that apps are ported to arm that our device is running it(you need to jailbreak your device to run them)
Click to expand...
Click to collapse
That is not the difference I was referring to....
Pls..Listen:
SixSixSevenSeven said:
That is not the difference I was referring to....
Click to expand...
Click to collapse
Winehq on an arm device mean:
-That we own an arm jailbroken windows_rt-like
-that we can run rt apps
.rootCoder. said:
Winehq on an arm device mean:
-That we own an arm jailbroken windows_rt-like
-that we can run rt apps
Click to expand...
Click to collapse
Your still wrong....
I know what it means. It seems to be you that does not.
WINE will run win32 applications. Not winRT applications.
Win32 = desktop.
WinRT = store.
Windows RT has both win32 and winrt runtimes. You are failing to specify which applications WINE will run on android, you just say windows RT, that could be store or desktop. The answer is desktop, you don't specify that.
SixSixSevenSeven said:
WINE does not support winrt at all. Only win32.
WINE does however support win32 on THUMB2 now and the wine wiki even directs you to GoodDayToDie's ported application thread. WINE can run these programs now.
It can do the ported desktop apps. It can't do store apps.
Click to expand...
Click to collapse
That is really cool! And even if Windows RT or Windows on ARM dies as far as the desktop is concerned (I hope not!), Linux on ARM can benefit from these compiled programs!
SixSixSevenSeven said:
Your still wrong....
I know what it means. It seems to be you that does not.
WINE will run win32 applications. Not winRT applications.
Win32 = desktop.
WinRT = store.
Windows RT has both win32 and winrt runtimes. You are failing to specify which applications WINE will run on android, you just say windows RT, that could be store or desktop. The answer is desktop, you don't specify that.
Click to expand...
Click to collapse
x86Apps=any windows x86 EXE files
arm rt ported apps=arm rt EXE files (for jailbroken ones)
So:
-you can run ARM ported EXE files on you rt(if it was jailbroken)
And:
Winehq is running on an arm device, so it well run that apps
AND: you're wrong windows rt HAS NOT win32 runtimes (see : http://download.microsoft.com/download/1/6/B/16B06F60-3B20-4FF2-B699-5E9B7962F9AE/VSU4/vcredist_arm.exe)
you well see that EXE app is for arm...so you can run it on your rt (if it was jailbroken) but..we can run it via wine on our arm device
domboy said:
That is really cool! And even if Windows RT or Windows on ARM dies as far as the desktop is concerned (I hope not!), Linux on ARM can benefit from these compiled programs!
Click to expand...
Click to collapse
Yup mate...you can do
i had did it and still doing it (only ARM EXEs...wine is not an emulator)
.rootCoder. said:
x86Apps=any windows x86 EXE files
AND: you're wrong windows rt HAS NOT win32 runtimes (see ...)
you well see that EXE app is for arm...so you can run it on your rt (if it was jailbroken) but..we can run it via wine on our arm device
Click to expand...
Click to collapse
No. You're wrong. WinRT != Windows RT. Amen. WinRT reffers to runtime of Metro Apps, they does not have .exe files.
http://en.wikipedia.org/wiki/Windows_Runtime
Win32's are just 32bit Windows Desktop Apps. And those are .exe's. They refer both to ARM and x86 CPU. You can run Win32 ARM (well, Thumb 2) apps.
Windows RT has Win32 runtime. You're linking to Visual C++ 2013 redistributable (version 12), 2012 (version 11) is included in OS.
Anyway, still - cool news, and another reason to get mingw working for arm/thumb2 But I'll stick to my XPS10.
kitor said:
No. You're wrong. WinRT != Windows RT. Amen. WinRT reffers to runtime of Metro Apps, they does not have .exe files.
http://en.wikipedia.org/wiki/Windows_Runtime
Win32's are just 32bit Windows Desktop Apps. And those are .exe's. They refer both to ARM and x86 CPU. You can run Win32 ARM (well, Thumb 2) apps.
Windows RT has Win32 runtime. You're linking to Visual C++ 2013 redistributable (version 12), 2012 (version 11) is included in OS.
Anyway, still - cool news, and another reason to get mingw working for arm/thumb2 But I'll stick to my XPS10.
Click to expand...
Click to collapse
OK...see : http://forum.xda-developers.com/showthread.php?p=36534446
those apps are ported arm EXEs(not x86) and they can be opened by both windows_rt and wine on arm devices
i've plaied prBOOM rt port and it's fully working
Sigh... lots of arguing about terminology and misinformation in this thread.
For everybody saying .rootCoder. is wrong: I don't see anywhere that he (or she) explicitly said WinRT, and in fact I do see a number of places he said "windows rt". "rt apps" (or "rt_apps") could apply to either. Oh, and WinRT EXEs are perfectly possible and indeed common; any native-code WinRT application will compile to an EXE (on desktop, tablet, or even phone).
GoodDayToDie said:
I don't see anywhere that he (or she) explicitly said WinRT, and in fact I do see a number of places he said "windows rt". "rt apps" (or "rt_apps") could apply to either.
Click to expand...
Click to collapse
Well, you're right (and apologies to OP), I just reread the thread and indeed .rootCoder. nowhere used "WinRT" name.
GoodDayToDie said:
Sigh... lots of arguing about terminology and misinformation in this thread.
For everybody saying .rootCoder. is wrong: I don't see anywhere that he (or she) explicitly said WinRT, and in fact I do see a number of places he said "windows rt". "rt apps" (or "rt_apps") could apply to either. Oh, and WinRT EXEs are perfectly possible and indeed common; any native-code WinRT application will compile to an EXE (on desktop, tablet, or even phone).
Click to expand...
Click to collapse
I never said he did say WinRT. He stated windows RT apps, that could be desktop or store and he wouldnt clarify which
SixSixSevenSeven said:
I never said he did say WinRT. He stated windows RT apps, that could be desktop or store and he wouldnt clarify which
Click to expand...
Click to collapse
I am pretty sure it is obvious he is talking about desktop apps, since he mentioned the jailbreak several times.
.rootCoder. said:
curruntly tested apps by me :
-bochsx86emu
-prboom
-quake
-A process manager
Click to expand...
Click to collapse
These are Windows RT "applications". Not Windows RT "apps". It don't have a same meaning nowaday.
Oh, bull. Yes, those are referred to as apps, but so are desktop computer software program(me)s, to use a number of terms that don't contain the string "app"... and which have been called "applications" or "apps" since at least the 90s and probably longer. Unless somebody specifies "Metro" or "Modern" apps, using the word "apps" to refer to desktop apps is perfectly valid. Calling it wrong isn't even pedantic, just incorrect. It should have been perfectly obvious what was being referred to.
Since windows can already run on snapdragon 835,i want to try it out on my mi6.
Is it possible and if so how to do it?
xpirad said:
Since windows can already run on snapdragon 835,i want to try it out on my mi6.
Is it possible and if so how to do it?
Click to expand...
Click to collapse
We need to have bios for our devices to boot it directly and since we don't have one, our best choice is to wait for a project on xda (I don't remember the name well but I'm pretty sure you can find easily if you search for it) that ports bios for android devices.
But to be honest even if you can run windows on mi 6 there are 2 bad news for you:
1) The vast majority of windows applications are written for x86 architecture and we have arm architecture, so to run them you should emulate either os or run the app in an emulated sandbox - so no good performance.
2) As I said in 1st one, emulation is a must (if you aren't planning to compile all those apps for arm architecture). Also windows 10's capability of running x86 apps on arm is based on that very emulation method, it runs them on a WoW (Windows on Windows) so there's clearly a hit on performance.
I suggest you to not to expect to have a decent windows system running on your arm device but if you need/want to run more basic windows apps, you can try Limbo PC Emulator. That way you can run some older or stripped down versions of windows with no heavy performance loss. For most of the basic things I find MicroXP project enough but don't expect to be able to run Photoshop on that I hope this answers your question.
I see, thank you ccelik97 for your clear answer.
I used to have some SDKs and even a WDK for Windows 10 (Including Windows 10 Mobile). After recently installing Visual Studio 2015/2017 and building up libraries tools etc. one install after another I was able to acquire SDKs, ADKs and WDKs for Windows Phone 7, WP 8.0 and WP 8.1....but when I got started on installing or trying to install Windows 10 (Including Win10m) I realized none of the downloads on M$'s servers/webpages contain the Windows 10 Mobile portion of the installations, after doing a quick google search it appears Microsoft removed Win10m development feaures from their product downloads as far back as 2017?? Has it really been that long...? Wow.... I know I can't have been the only one to download these dev kits while they were available, can anybody provide a backup link or archive link to a cloud based service to share for those of us that still wish to continue to build Win10m source files and mess around with creating our own (UWP or not) Win10m software??
Thanks very much guys
Hi guys, can anyone help to install Windows 10 for ARM32 for Nokia Lumia 2520 RT tablet?
Same procedure as other devices but you will have to substitute the drivers with ones from the 2520 aside from qcpep which has to be replaced with an alternative one which I think came from the Lumina WoA project staff (From Lumia 930?). However, if your 2520 has been kept up to date with the latest patches under RT 8.1 then you won't be able to jailbreak it in order to use 15035
jwa4 said:
However, if your 2520 has been kept up to date with the latest patches under RT 8.1 then you won't be able to jailbreak it in order to use 15035
Click to expand...
Click to collapse
Hi JWA4 could you expand on this? Also is it the case for the surface RT as well (latest up to date version can't be jailbreaked) or just the 2520?
devinpatterson said:
Hi JWA4 could you expand on this? Also is it the case for the surface RT as well (latest up to date version can't be jailbreaked) or just the 2520?
Click to expand...
Click to collapse
The short version as I understand it is that Nvidia screwed up in users favor which makes the Tegra Surfaces immune to permanent effects of the jailbreak killing Windows RT updates. On these devices reversing the negative effects of theses updates is as simple as a factory reset.
Sadly with the Lumia 2520, Qualcomm did the job right and at present there is no going back if a jailbreak killer has ever been installed.
I will try to find the detailed explanation I read and post it here asap.
jwa4 said:
The short version as I understand it is
Click to expand...
Click to collapse
Thanks for taking the time to fill me in the 2520 Jwa4
jwa4 said:
I will try to find the detailed explanation I read and post it here asap.
Click to expand...
Click to collapse
That would be awesome if your able to locate the info in more detail
devinpatterson said:
That would be awesome if your able to locate the info in more detail
Click to expand...
Click to collapse
I was unable to find the explanation that I read but if I find it again I will post.
I could be wrong and there might be more to it but I think the general idea was that Nvida did not implement the mechanism that handles the revocation of previously issued certificates correctly whereas Qualcomm did. On a previously updated Lumia 2520 this prevents the Secure Boot Debug Policy from working because its certificate is no longer going to be valid on the device.
Telegram: Contact @L2520w10RT
4pda.ru
I installed Win 10 RT on Lumia 2520.
with any security updates! No problem.
But, I need help with drivers.
CageOff said:
Telegram: Contact @L2520w10RT
4pda.ru
I installed Win 10 RT on Lumia 2520.
with any security updates! No problem.
But, I need help with drivers.
Click to expand...
Click to collapse
How were you able to do this? I thought the Secure Boot issue stopped any other installations?
lord_melchett said:
How were you able to do this? I thought the Secure Boot issue stopped any other installations?
Click to expand...
Click to collapse
Go to Discord. I discuss all the sub-genes there. The system is not ready for public use. Testsign, secureboot and everything you need is there. No problem using Linux via grub uefi. It is much more difficult to find developers who will do this. And Tales about the impossibility of disabling Secureboot is just a fact of bygone days. The device is now free of these restrictions.
No touch, no modem, no BT, no audio, adreno 330 not work.
But yesterday qcpep and qcpepproxy did not work as expected.
Today they are working as expected.
I will start other hardware devices too. It just takes time.
CageOff said:
Go to Discord. I discuss all the sub-genes there. The system is not ready for public use. Testsign, secureboot and everything you need is there. No problem using Linux via grub uefi. It is much more difficult to find developers who will do this. And Tales about the impossibility of disabling Secureboot is just a fact of bygone days. The device is now free of these restrictions.
No touch, no modem, no BT, no audio, adreno 330 not work.
But yesterday qcpep and qcpepproxy did not work as expected.
Today they are working as expected.
I will start other hardware devices too. It just takes time.
Click to expand...
Click to collapse
Cool. So does everything work fine on Linux, just not in Windows 10? Having never used discord let me know where to find out. If I can dump any files to help let me know
CageOff said:
[URL unfurl = "true"] https://4pda.ru/pages/go/?u=https://t.me/L2520w10RT&e=103134199&f=https://4pda.ru/forum/index .php% 3Fshowtopic% 3Dst5135 [/ URL]
Ho installato Win 10 RT su Lumia 2520.
con eventuali aggiornamenti di sicurezza! Nessun problema.
Ma ho bisogno di aiuto con i conducenti.
Click to expand...
Click to collapse
Salve...mi potreste aiutare ad aistallare windows 10 oppure linux mine su nokia lumia 2520?
Salve ragazzi ... vorrei un aiuto per istallare windows 10 o linux mine su nokia lumia 2520 ... se è possibbile..grazie..questo forum e fantastico ... max
Do you have a guide to follow for this? I went to your Telegram site but all I saw was pictures.
i need help to install windows 10 rt on Nokia 2520
I know this device is so outdated and all, yet it'd be nice to get some use out of it. Anyone have a proper guide on how to accomplish what @CageOff was saying in order to bypass the security update patches and getting securebooot unlocked. I've tried so many different methods and gotten nowhere in my attempts to get working BOOTABLE USB media for 8.1. No guide clearly explains/points out that the Myriachan's Jailbreak is the exploit specifically intended for the Qualcomm Nokia Lumia 2520 to get the test mode exploit going (if it works). Longhorn obviously doesn't work as it can't install Golden Keys. I went to the Telegram group @CageOff mentions, but there is no way to talk to the person nor any clear info about how he managed to dualboot win10 arm/win8.1 arm. If anyone could shed some light on me here, It'd be much appreciated.
hugoBOSS1981 said:
I know this device is so outdated and all, yet it'd be nice to get some use out of it. Anyone have a proper guide on how to accomplish what @CageOff was saying in order to bypass the security update patches and getting securebooot unlocked. I've tried so many different methods and gotten nowhere in my attempts to get working BOOTABLE USB media for 8.1. No guide clearly explains/points out that the Myriachan's Jailbreak is the exploit specifically intended for the Qualcomm Nokia Lumia 2520 to get the test mode exploit going (if it works). Longhorn obviously doesn't work as it can't install Golden Keys. I went to the Telegram group @CageOff mentions, but there is no way to talk to the person nor any clear info about how he managed to dualboot win10 arm/win8.1 arm. If anyone could shed some light on me here, It'd be much appreciated.
Click to expand...
Click to collapse
Myriachan is not specifically intended for Qualcomm devices, its just that it can't be permanently patched against but this won't help you for 15035.
I don't have a 2520 but from what I can tell CageOff seems to have booted 15035 on a 2520 but the details are getting lost in translation and a writeup doesn't seem to be forthcoming. From what I can gather even though he has booted 15035 on his 2520, he has done so without the installation of the QCPEP driver and without this driver virtually nothing else will work.
On QCEP - BetaWiki.net
This build does not support the Nokia Lumia 2520 Qualcomm Power Engine Plugin driver. Loading a newer driver for the Snapdragon 800 is mandatory.
Click to expand...
Click to collapse
The newer driver I believe is harvested from the LumiaWOA project, specifically taken from the Lumia 930 package. It could be worth looking at how WFAv7_Installer installs 15035 on a 930? It might shed some light on the driver ordering, as far as I've been told Qualcomm stuff has to be dealt with in a certain order.
Before you put too much time in to this though remember 15035 is about as much use a chocolate teapot so remember its just for fun. If you spend a week figuring it and actually get it all working in the hope of making an ex-RT device useful you are going to be a little disappointed at the end of it.
jwa4 said:
Myriachan is not specifically intended for Qualcomm devices, its just that it can't be permanently patched against but this won't help you for 15035.
I don't have a 2520 but from what I can tell CageOff seems to have booted 15035 on a 2520 but the details are getting lost in translation and a writeup doesn't seem to be forthcoming. From what I can gather even though he has booted 15035 on his 2520, he has done so without the installation of the QCPEP driver and without this driver virtually nothing else will work.
On QCEP - BetaWiki.net
The newer driver I believe is harvested from the LumiaWOA project, specifically taken from the Lumia 930 package. It could be worth looking at how WFAv7_Installer installs 15035 on a 930? It might shed some light on the driver ordering, as far as I've been told Qualcomm stuff has to be dealt with in a certain order.
Before you put too much time in to this though remember 15035 is about as much use a chocolate teapot so remember its just for fun. If you spend a week figuring it and actually get it all working in the hope of making an ex-RT device useful you are going to be a little disappointed at the end of it.
Click to expand...
Click to collapse
That's definitely worth looking into in regards to the "WFAv7_Installer". I just tried the WOA Deployer v2.7.1 and it seems it could be of great use in getting Win 10/11 arm onto this device. Of course, if one can figure out how to access/enter a Mass Storage mode first.
I also read in another forum article that the IOT versions of Windows seems to be more useful for this device, rather than trying to get the standard Pro/Home editions. They also mentioned that one may need to apply the drivers from the original Win 8.1 RT in order to get all of the devices hardware working though. I would personally like to give this a try, but I can't seem to get to the point of being able to install Win 10 build 15035 onto my device. I can't enable test-signing mode, nor disable bootloader with any of the jail breaks available. I get the error code 0x000000000000d (not sure i put the correct amount of zero's there), which seems to give no existing info on the net for that error code, only a few forum posts regarding the variant to that code which ends in "f" which seems to be related to the Surface 1/2 devices.
I know I can format the eMMC properly via command prompt, diskpart, and dism (for Win 8.1 RT), then disable BitLocker (even though C:\ still says Bitlocker Encrypted). Yet, I just can't get the Win 10 media to work which i assume is due to secure boot. Does it make any difference if I'm using the install.wim or install.esd versions of the media?
hugoBOSS1981 said:
That's definitely worth looking into in regards to the "WFAv7_Installer". I just tried the WOA Deployer v2.7.1 and it seems it could be of great use in getting Win 10/11 arm onto this device. Of course, if one can figure out how to access/enter a Mass Storage mode first.
Click to expand...
Click to collapse
WOA Deployer is specifically for deploying WoA on the Lumia 950 & 950 XL, it doesn't support Windows 10 15035 or ARM32 devices like the Lumia 2520.
Windows 11 is out of the question, only small parts of it were built for ARM32 (nothing close to a full client) and the bits that were built won't work with this SoC. I don't believe WFAv7_Installer ever had the 2520 in mind, I only suggested it because how it prepares an image for some of the Lumia phones might shed some light on how an image would need to be prepared for the 2520.
hugoBOSS1981 said:
I also read in another forum article that the IOT versions of Windows seems to be more useful for this device, rather than trying to get the standard Pro/Home editions. They also mentioned that one may need to apply the drivers from the original Win 8.1 RT in order to get all of the devices hardware working though.
Click to expand...
Click to collapse
That's going to come down to what you define as useful but personally I don't see any point in running IoT on a tablet. At the time of writing only the 15035 client build is available and that's now over five years old. Drivers taken from the RT 8.1 recovery image would be required along with the replacement PEP driver mentioned previously but its possible not all drivers will be compatible with IoT.
hugoBOSS1981 said:
I would personally like to give this a try, but I can't seem to get to the point of being able to install Win 10 build 15035 onto my device. I can't enable test-signing mode, nor disable bootloader with any of the jail breaks available. I get the error code 0x000000000000d (not sure i put the correct amount of zero's there), which seems to give no existing info on the net for that error code, only a few forum posts regarding the variant to that code which ends in "f" which seems to be related to the Surface 1/2 devices.
Click to expand...
Click to collapse
To enable test mode you would need either Golden Keys or the Myriachan jailbreak, unless you are lucky then the device you have might not be capable of using Golden Keys anymore. If I'm remembering correctly the Myriachan jailbreak is only useful for running third party applications under RT 8.1 and wouldn't assist in running another OS.
hugoBOSS1981 said:
I know I can format the eMMC properly via command prompt, diskpart, and dism (for Win 8.1 RT), then disable BitLocker (even though C:\ still says Bitlocker Encrypted). Yet, I just can't get the Win 10 media to work which i assume is due to secure boot. Does it make any difference if I'm using the install.wim or install.esd versions of the media?
Click to expand...
Click to collapse
Windows 10 15035 isn't available as an ESD, you would need to take the 15035 installation files and properly add the drivers to boot.wim, install.wim and winre.wim before copying them to USB and attempting the installation. CageOff seems to have installed 15035 without the use of Golden Keys but even when booted the installation of 15035 is useless because he has not added the PEP driver.
A clean 15035 if you don't have one (No drivers):
Windows 10 Enterprise Build 15035 ARMv7 : Microsoft : Free Download, Borrow, and Streaming : Internet Archive
Windows 10 Enterprise Build 15035 ARMv7
archive.org
Lumia 2520 Drivers (Extracted from RT 8.1 Recovery Media):
Lumia_2520_Drivers.zip - AnonFiles
anonfiles.com
Replacement qcpep / qcpepproxy from Lumia project for 15035:
Lumia_930_qcpep.zip - AnonFiles
anonfiles.com
I don't know much at all about the 2520 and pretty much anything I say about it could be wrong
Hi to all, i've bought a Surface RT on ebay and once it arrived it was in factory reset. MS Store and Update aren't working because the support for RT 8 was discontinued, and i can't get nor the updates for RT 8 nor the upgrade to RT 8.1. Explorer can't open pages because it's too old and every other preinstalled app can't be updated. I don't know what to do with this tablet. All the guides or Updates i've found searching on the internet all speaks all about RT 8.1. I tried to install those updates but (obviously) aren't working.
Can somebody help me and tell me if there is a way to install the version 8.1 or how to get the best out of this tablet in the current state?
Thank you
You can make an updated recovery image using this:
Windows RT 8.1 IR5 Media Builder
17/12/2020 - Windows_RT_8.1_IR5_Update_Kit_v1.6.zip 17/12/2020 - Windows_RT_8.1_IR5_Update_Kit_v1.6_Appx.zip - Added three additional update modes (None, Service Stack Only & Service Stack and Update 3 Only). - Added warning for languages that do...
forum.xda-developers.com
But its worth noting a fully updated RT isn't exactly useful, the browser is out of date, the store is unreliable etc.
jwa4 said:
You can make an updated recovery image using this:
Windows RT 8.1 IR5 Media Builder
17/12/2020 - Windows_RT_8.1_IR5_Update_Kit_v1.6.zip 17/12/2020 - Windows_RT_8.1_IR5_Update_Kit_v1.6_Appx.zip - Added three additional update modes (None, Service Stack Only & Service Stack and Update 3 Only). - Added warning for languages that do...
forum.xda-developers.com
But its worth noting a fully updated RT isn't exactly useful, the browser is out of date, the store is unreliable etc.
Click to expand...
Click to collapse
i'll try this and post the result, thank you
I tried to run the Windows RT 8.1 IR5 Media Builder, but it's not working. It keeps saying unsupoorted OS