Hey guys! Today in my mind a BLING sounded, and i thought:
If it's possible to install windows IoT core on surface, instead of disabling the UEFI, we can copy the key in windows IoT core that show the surface windows IoT core is a windows OS
It's possible?
roxas22 said:
Hey guys! Today in my mind a BLING sounded, and i thought:
If it's possible to install windows IoT core on surface, instead of disabling the UEFI, we can copy the key in windows IoT core that show the surface windows IoT core is a windows OS
It's possible?
Click to expand...
Click to collapse
I don't care about installing another Windows. I think Ubuntu with microsoft key signed in its 1st stage EFI bootloader(idk much about bootloader) can boot in surface rt even with secure boot enabled!
Options for Installing Linux
You have several options for installing Linux on a PC with Secure Boot:
•Choose a Linux Distribution That Supports Secure Boot: Modern versions of Ubuntu — starting with Ubuntu 12.04.2 LTS and 12.10 — will boot and install normally on most PCs with Secure Boot enabled. This is because Ubuntu’s first-stage EFI boot loader is signed by Microsoft. However, a Ubuntu developer notes that Ubuntu’s boot loader isn’t signed with a key that’s required by Microsoft’s certification process, but simply a key Microsoft says is “recommended.” This means that Ubuntu may not boot on all UEFI PCs. Users may have to disable Secure Boot to to use Ubuntu on some PCs.
•Disable Secure Boot: Secure Boot can be disabled, which will exchange its security benefits for the ability to have your PC boot anything, just as older PCs with the traditional BIOS do. This is also necessary if you want to install an older version of Windows that wasn’t developed with Secure Boot in mind, such as Windows 7.
•Add a Signing Key to the UEFI Firmware: Some Linux distributions may sign their boot loaders with their own key, which you can add to your UEFI firmware. This doesn’t seem to be a common at the moment.
You should check to see which process your Linux distribution of choice recommends. If you need to boot an older Linux distribution that doesn’t provide any information about this, you’ll just need to disable Secure Boot.
You should be able to install current versions of Ubuntu — either the LTS release or the latest release — without any trouble on most new PCs. See the last section for instructions on booting from a removable device.
Click to expand...
Click to collapse
Source :- http://www.howtogeek.com/175641/how-to-boot-and-install-linux-on-a-uefi-pc-with-secure-boot/
Click to expand...
Click to collapse
You can try it if you want.
XDA-00 said:
I don't care about installing another Windows. I think Ubuntu with microsoft key signed in its 1st stage EFI bootloader(idk much about bootloader) can boot in surface rt even with secure boot enabled!
You can try it if you want.
Click to expand...
Click to collapse
If you did a search here, you'd see that Ubuntu does not work as we have a locked bootloader. Think of it like a Verizon galaxy S4 on KitKat, you cannot install cwm or twrp and custom roms until the bootloader is unlocked and open to modding. We have not reached that stage with Windows RT devices yet.
Sent from my Q5 using XDA Free mobile app
Qiangong2 said:
If you did a search here, you'd see that Ubuntu does not work as we have a locked bootloader. Think of it like a Verizon galaxy S4 on KitKat, you cannot install cwm or twrp and custom roms until the bootloader is unlocked and open to modding. We have not reached that stage with Windows RT devices yet.
Sent from my Q5 using XDA Free mobile app
Click to expand...
Click to collapse
Has anyone found the way to unlock bootloader on surface rt? If ubuntu supports only unlocked bootloader then what OS supports locked bootloader.
Will removing the tpm chip(from motherboard) remove bitlocker and secure boot?
XDA-00 said:
Has anyone found the way to unlock bootloader on surface rt? If ubuntu supports only unlocked bootloader then what OS supports locked bootloader.
Will removing the tpm chip(from motherboard) remove bitlocker and secure boot?
Click to expand...
Click to collapse
about the TPM, it's integrated in the SoC, so no
About unlocking the bootloader, yes, but I can't release it.
So why?
black_blob said:
about the TPM, it's integrated in the SoC, so no
About unlocking the bootloader, yes, but I can't release it.
Click to expand...
Click to collapse
Great work on the bootloader...but why spend the time to open the bootloader, shoehorn Windows 10 Mobile on there, and then not release the patch so people can do the same? I guess this proves that you can do it, but who cares, right?
Please don't sit in Windows 10 Mobile Versailles, and tell us to eat cake!
Will
willz06jw said:
Great work on the bootloader...but why spend the time to open the bootloader, shoehorn Windows 10 Mobile on there, and then not release the patch so people can do the same? I guess this proves that you can do it, but who cares, right?
Please don't sit in Windows 10 Mobile Versailles, and tell us to eat cake!
Will
Click to expand...
Click to collapse
The only thing that I can say is that I legally can't release it without being eaten.
black_blob said:
The only thing that I can say is that I legally can't release it without being eaten.
Click to expand...
Click to collapse
Just a question, is it a low-level kernel hack? Or is it just a security hole that you've exploited?
Sent from my Q5 using XDA Free mobile app
Qiangong2 said:
Just a question, is it a low-level kernel hack? Or is it just a security hole that you've exploited?
Sent from my Q5 using XDA Free mobile app
Click to expand...
Click to collapse
Backdoor left in development stages, which MS forgot to close.
black_blob said:
Backdoor left in development stages, which MS forgot to close.
Click to expand...
Click to collapse
Unlocking bootloader requires admin access?
black_blob said:
Backdoor left in development stages, which MS forgot to close.
Click to expand...
Click to collapse
Alright, but couldn't you at least sign a build of Ubuntu or whatever? So we can install it on our devices? Windows RT is useless, and thus RT devices are useless!
nar001 said:
Alright, but couldn't you at least sign a build of Ubuntu or whatever? So we can install it on our devices? Windows RT is useless, and thus RT devices are useless!
Click to expand...
Click to collapse
true that! :good:
MS16-094 aka CVE-2016-3287
So I guess this is what MS16-094 fixes? It's in this month's Patch Tuesday security fixes from Microsoft.
"A security feature bypass vulnerability exists when Windows Secure Boot improperly applies an affected policy. An attacker who successfully exploited this vulnerability could disable code integrity checks, allowing test-signed executables and drivers to be loaded on a target device. In addition, an attacker could bypass the Secure Boot Integrity Validation for BitLocker and the Device Encryption security features. To exploit the vulnerability, an attacker must either gain administrative privileges or physical access to a target device to install an affected policy. The security update addresses the vulnerability by blacklisting affected policies."
diodesign said:
So I guess this is what MS16-094 fixes? It's in this month's Patch Tuesday security fixes from Microsoft.
"A security feature bypass vulnerability exists when Windows Secure Boot improperly applies an affected policy. An attacker who successfully exploited this vulnerability could disable code integrity checks, allowing test-signed executables and drivers to be loaded on a target device. In addition, an attacker could bypass the Secure Boot Integrity Validation for BitLocker and the Device Encryption security features. To exploit the vulnerability, an attacker must either gain administrative privileges or physical access to a target device to install an affected policy. The security update addresses the vulnerability by blacklisting affected policies."
Click to expand...
Click to collapse
Yes, it's mine.
Note that it has nothing to do with the registry.
black_blob said:
Yes, it's mine.
Click to expand...
Click to collapse
Ah cool find - did you report it to Microsoft, they fixed it, and you're under NDA to not talk about it?
diodesign said:
Ah cool find - did you report it to Microsoft, they fixed it, and you're under NDA to not talk about it?
Click to expand...
Click to collapse
He wouldn't have told us initially if he was under an NDA from Microsoft.
Sent from my Q5 using XDA Free mobile app
Qiangong2 said:
He wouldn't have told us initially if he was under an NDA from Microsoft.
Sent from my Q5 using XDA Free mobile app
Click to expand...
Click to collapse
People really should just ignore black_bob, he seems to be just a typical internet attention seeker who actually seems to get off on the attention that getting peoples hopes up brings. If I'm wrong I'm sorry but I'm pretty sure black_bob has form for pulling this kind of crap (along with one or two others), I'm sure he is very talented but if he's not going to actually put anything out there then he needs to keep quiet.
HansuTuru said:
People really should just ignore black_bob, he seems to be just a typical internet attention seeker who actually seems to get off on the attention that getting peoples hopes up brings. If I'm wrong I'm sorry but I'm pretty sure black_bob has form for pulling this kind of crap (along with one or two others), I'm sure he is very talented but if he's not going to actually put anything out there then he needs to keep quiet.
Click to expand...
Click to collapse
Wait for next month's Patch Tuesday first.
[Removed]
Guys guys guys GUYS, i think i seek an exploit, PM for infos
Related
Hi guys !
I wanted to know whether the new Samsung Galaxy Tab 3 10.1 can run Windows 8./LINUX !!
Theoretically it shouldn't be too hard as it has an Intel Atom x86 processor and it shares a lot of it's specs with the Acer Iconia w510 and other tablets running Windows 8
Can you please tell me some of the issues that we may have to deal with ?
Like we will have to do something with the bootloader to make Windows 8 bootable and things like that :/
And please if you want to say something like -Why do you want to run windows on an Android tablet-
XDA is about modding. A new OS will not hurt anyone AFAIK.
What are your ideas ? I think it can be done but what will we need to do ?
Now we will be concentrating on Linux. it Will be easier.
Please use this thread for discussing Linux on the Samsung Galaxy Tab 3 10.1
Thanks for reading !
Nitro_123 said:
Hi guys !
I wanted to know whether the new Samsung Galaxy Tab 3 10.1 can run Windows 8.
Theoretically it shouldn't be too hard as it has an Intel Atom x86 processor and it shares a lot of it's specs with the Acer Iconia w510 and other tablets running Windows 8
Can you please tell me some of the issues that we may have to deal with ?
Like we will have to do something with the bootloader to make Windows 8 bootable and things like that :/
And please if you want to say something like -Why do you want to run windows on an Android tablet-
XDA is about modding. A new OS will not hurt anyone AFAIK.
What are your ideas ? I think it can be done but what will we need to do ?
Thanks for reading !
Click to expand...
Click to collapse
much like apple windows 8 is closed source. Thats pretty much the end of the thread. Without a way to compile, edit the operating system and know what changes your making its just not a undertaking many will accept.
@trevd Do you have anything to say about this ?
@wranglerray I'm just talking about installing windows to a device. AFAIK no compiling/editing will be needed. There are other tablets out there that do the same thing so why not this one ? The only major hurdle I see is making some kind of a custom bootloader that can boot the windows stuff instead of the android stuff. THAT part will probably need to be made from scratch or it may be ported from a similar device.
There are quite a few devices like this that run windows with similar specs so why not this one ?
Nitro_123 said:
@trevd Do you have anything to say about this ?
@wranglerray I'm just talking about installing windows to a device. AFAIK no compiling/editing will be needed. There are other tablets out there that do the same thing so why not this one ? The only major hurdle I see is making some kind of a custom bootloader that can boot the windows stuff instead of the android stuff. THAT part will probably need to be made from scratch or it may be ported from a similar device.
There are quite a few devices like this that run windows with similar specs so why not this one ?
Click to expand...
Click to collapse
well quite honestly your talking about porting windows to a device. Our device comes with android and you want to port windows to it instead. So on our device there are parititons chuncks of data of varying sizes allocated to hold a small part of the code that runs our phone. from ramdisk to the radio. The issue on its surface, we dont know how that partition table lines up with a different device.(which the partition table can and most likely is, completely different) and because winodws 8 is closed source we dont know how it boots, or how to edit the imstaller to ensure the os gets copied over the correct partitions. if porting were as easying as just flashing what ever you want and then changing some things to tweak it i'm sure you'd see hundreds of ports in a day or two. Unforntatley it really kinda sucks
The partitions are the biggest problem. We could in theory also boot from the SD card and as a result bypass all the android stuff and get it dual-booting but first we need to know how we can boot windows
Nitro_123 said:
@trevd Do you have anything to say about this ?
Click to expand...
Click to collapse
Hi There
I've not got a device in my hands yet to be able to give a proper device focused opinion on this.
but since you ask, I will say It really all depends on the bootloader setup on the device and how accessible that is, it could well be a proprietary Samsung Design in which case I wouldn't want to "mess" with it unless you had a JTag handy for when s**t goes wrong, otherwise you'll be holding a very expensive brick.
Even without bootloader access theoretically you could create a 3rd stage bootloader ( possibly Grub2/uboot ) which sits in place of the kernel in the boot image ( or recovery image ) , this would give the Option to load android or chainload into the windows boot manager, this is how things are done on classic x86.
If you have to go with a 3rd Stage Loader then the first steps is to get your own code running instead of the Standard Kernel Initialization inside an android boot image, There's all sorts of fun to be had after that as basically you'd need to place things in memory where the Kernel or the Boot Manager is expecting to find them amongst many other things.
Standard Windows 7/8 Installations setup a "hidden ( not assigned a drive letter in windows) " 100MB NTFS partition which contains the bootmgr.exe ( TRIVIA : boot manager replaced NT LOADER ( NTLDR ) which was used by Windows XP ). The boot configuration datafile ( BCD ) contains the settings for loading the actual operating system.
I wouldn't be too concerned about the closed source nature of Windows as there's still plenty of folks doing some absolutely bonkers **** with Windows/Windows Booting. Check out http://reboot.pro if you want to see some of that. My favourite is the 10MB WindowsXP that boots cmd.exe and nothing else LOL WAT!?! . I'm not saying you'll find the answers there but I'd consider it the "state of the art" when booting windows in unusual ways.
Without getting too far ahead, if you did get it booting then it appears the Asus Memo Pad FHD 10 which is a windows 8 device has the same SOC so I would expect there to be driver support already present ( or available ).
Additionally I've not even considered UEFI and how that would affect the whole scenario as I've not delved into the UEFI chaos yet.
Personally I've not used Windows in anger for a couple of years and I've only booted Windows 8 in VM's just to have a look, so my "WindowsFu" is getting a little rusty.
In Summary : Technically Possible ( anything is possible ) - All depends on the bootloader and how much you want it! and to paraphrase @wranglerray "If it was easy, everyone would be doing it"
Trevd
@trevd @wranglerray Thanks so much for the input
This shouldn't really be too hard to do for an experienced dev IMO but I don't have mcuh experience with all this stuff
The stuff that has been done to the HD2 was a lot harder I think but Cotulla still managed to make a custom bootloader and boot WP7 things like that
Thanks again for the comments
@wranglerray @trevd
http://forum.xda-developers.com/showthread.php?t=2540480
Please read the above link
basically we can now understand what the partitions are and what they do
Is it really that hard to make some kind of a zip file that can be flashed in recovery to boot the windows 8 bootloader ?
Why can't we just install an image of windows 8 to the SD card and boot off it ?
What do I need to know in order to understand and try to make this work ? Since no one is developing for the tab 3 10.1 I thought I'd give it a try
Nitro_123 said:
@wranglerray @trevd
http://forum.xda-developers.com/showthread.php?t=2540480
Please read the above link
basically we can now understand what the partitions are and what they do
Is it really that hard to make some kind of a zip file that can be flashed in recovery to boot the windows 8 bootloader ?
Why can't we just install an image of windows 8 to the SD card and boot off it ?
What do I need to know in order to understand and try to make this work ? Since no one is developing for the tab 3 10.1 I thought I'd give it a try
Click to expand...
Click to collapse
As a newbee I will guess:
Windows can take a bigger effort.
Runing Linux natively, easier. Android drivers should be already Linux Compatible. Tweeking them under Linux I do not know. My best guess is looking how to make grub to run first for dual booting. Or even better, Create a partition on external SD forl Linux, To be safe on TWRP recovery add a bottom to boot Linux or even esier re-use one temporary to test posibility.
Good Luck.
dale_para_bajo said:
As a newbee I will guess:
Windows can take a bigger effort.
Runing Linux natively, easier. Android drivers should be already Linux Compatible. Tweeking them under Linux I do not know. My best guess is looking how to make grub to run first for dual booting. Or even better, Create a partition on external SD forl Linux, To be safe on TWRP recovery add a bottom to boot Linux or even esier re-use one temporary to test posibility.
Good Luck.
Click to expand...
Click to collapse
@dale_para_bajo EXACTLY my friend. You stole the words right out of my mouth
Objective: Get Linux booting. SD card way is better.
Any updates on this?
SharpnShiny said:
Any updates on this?
Click to expand...
Click to collapse
It will never happen, the firmware isn't compatible.
calden74 said:
It will never happen, the firmware isn't compatible.
Click to expand...
Click to collapse
Yeah I've looked a bit more into it since, I think the best chance was Windows RT, and that isn't downloadable I believe, so that's it. Thanks for the reply though.
SharpnShiny said:
Yeah I've looked a bit more into it since, I think the best chance was Windows RT, and that isn't downloadable I believe, so that's it. Thanks for the reply though.
Click to expand...
Click to collapse
Even if Windows RT aka an ARM optimized ISO, was downloadable, it COULD NOT be used on Tab 3 10.1
Because this Tab doesn't have an ARM CPU, it have a x86 (32Bits) CPU. So better get a x86 ISO. I also got the same idea (like many other Tab 3 10.1 users). But the dream is NOT going anywhere. Also, Android apps are honestly BAD OPTIMIZED for this CPU ! That's why the Tab lags.
I sold mine and have bought a Tab 7.7 w/ SuperAmoled HD Screen but I broke its screen and can't now find any replacement in my region
Our best chance would be:
Ability of instally Windows 8 into a single .IMG file like Windows XP has been installed !
However, QEMU and KVM refuses to install Windows 8 into a VM idk why !
The RAM of the Tab is also a bit low to run Windows 8 inside Android.
If only a Great Dev could port or create "The Multi-boot bootloader" for Tab 3 10.1 as done on Nexus 7, then I won't waste my money buying a Windows 8 Tablet again since I would manage to install Windows 8 natively, whatever happened !
Sent from my roomate's computer
Can this work?
trevd said:
Hi There
I've not got a device in my hands yet to be able to give a proper device focused opinion on this.
but since you ask, I will say It really all depends on the bootloader setup on the device and how accessible that is, it could well be a proprietary Samsung Design in which case I wouldn't want to "mess" with it unless you had a JTag handy for when s**t goes wrong, otherwise you'll be holding a very expensive brick.
Even without bootloader access theoretically you could create a 3rd stage bootloader ( possibly Grub2/uboot ) which sits in place of the kernel in the boot image ( or recovery image ) , this would give the Option to load android or chainload into the windows boot manager, this is how things are done on classic x86.
If you have to go with a 3rd Stage Loader then the first steps is to get your own code running instead of the Standard Kernel Initialization inside an android boot image, There's all sorts of fun to be had after that as basically you'd need to place things in memory where the Kernel or the Boot Manager is expecting to find them amongst many other things.
Standard Windows 7/8 Installations setup a "hidden ( not assigned a drive letter in windows) "* 100MB NTFS partition which contains the bootmgr.exe ( TRIVIA : boot manager replaced NT LOADER (* NTLDR ) which was used by Windows XP ). The boot configuration datafile ( BCD )* contains the settings for loading the actual operating system.
I wouldn't be too concerned about the closed source nature of Windows as there's still plenty of folks doing some absolutely bonkers **** with Windows/Windows Booting. Check out httpdouble slash)reboot(dot)pro if you want to see some of that. My favourite is the 10MB WindowsXP that boots cmd.exe and nothing else LOL WAT!?! . I'm not saying you'll find the answers there but I'd consider it the "state of the art" when booting windows in unusual ways.
Without getting too far ahead, if you did get it booting then it appears the Asus Memo Pad FHD 10 which is a windows 8 device has the same SOC so I would expect there to be driver support already present ( or available ).
Additionally I've not even considered UEFI and how that would affect the whole scenario as I've not delved into the UEFI chaos yet.
Personally I've not used Windows in anger for a couple of years and I've only booted Windows 8 in VM's just to have a look, so my "WindowsFu" is getting a little rusty.
In Summary : Technically Possible ( anything is possible ) - All depends on the bootloader and how much you want it! and to paraphrase** @wranglerray "If it was easy, everyone would be doing it"
Trevd
Click to expand...
Click to collapse
I am new to the forum but not windows and android though not advanced but do you think that getting those files in the 100mb partition and making an ext2 image of them with slight modifications to fit in the architecture and flash the image as a recovery image?
or perhaps we could use rom manager and by creating a virtual rom composing of windows and boot them via the rom manager tool.
or perhaps we could use grub or a similar tool to boot into an image file or sdcard with windows installed on it and flash the grub files onto the recovery partition but some one with advanced info please confirm all these possibilities!
________________________________________________________________________________________
Hit thanks if I helped, its not that tough
Go ahead guys !
This thread is becoming IRRELEVANT !
Tab 3 was made to run Android (and possibly Ubuntu since Android is a mobile version of Linux) but NOT Windows !
So just use Android or Nothing.
Sent from my roomate's computer
yes but
Nonta72 said:
Go ahead guys !
This thread is becoming IRRELEVANT !
Tab 3 was made to run Android (and possibly Ubuntu since Android is a mobile version of Linux) but NOT Windows !
So just use Android or Nothing.
Sent from my roomate's computer
Click to expand...
Click to collapse
Yes, but since both Windows and any x86 Linux are designed for the same architecture, shouldn't we be able to boot Windows?
glorified sd card
Dani515 said:
Yes, but since both Windows and any x86 Linux are designed for the same architecture, shouldn't we be able to boot Windows?
Click to expand...
Click to collapse
i think it's possible
check this out starting at angel_666's post #18
http://forum.xda-developers.com/showthread.php?t=2589370&page=2
finding out where the flag checking starts and finishes would probably make the third stage boot
more realizeable. i directly flashed both grub and then plop to recovery block and got nowhere,
so it's mmcblk0boot0 or mmcblk0boot1, i haven't found anything in param===>/dev/block/mmcblk0p16 yet
and if p5210 has the little kernel burnt onto the chip setup, from my understanding of what i've
read it's a really basic/small/simple setup so even if the flag was there and unchangeable we should
still be able to get past it somewhere else, right?
Really ?
Dani515 said:
Yes, but since both Windows and any x86 Linux are designed for the same architecture, shouldn't we be able to boot Windows?
Click to expand...
Click to collapse
I firstly got this idea and have posted here on XDA about it :good:
Look at this thread http://forum.xda-developers.com/showthread.php?t=2682603
However, mine was about running Windows 8 inside Android
Sent from my roomate's computer
Done already?
Hello,
I have found this thread: http://forum.xda-developers.com/showthread.php?t=2070139
If you read further, you can find almost complete solution for archlinux natively on Note 10.1. WIth multiple fixes/scripts. Any reason why it cannot be done on tab3 10.1? I'm asking because I might try to compile proper kernel and prepare some distribution as tablet provides power that ends up completely wasted by android.
I tried to run Windows 10 IoT from RPi2 on the Surface RT with included drivers from Surface RT. Appears BDOS error CRITICAL_PROCESS_DIED. Maybe someone will change something? To run the system, unpack the archive on the USB-stick formatted in FAT32.
For launch on Surface RT, turn off the device, hold Vol- and press Power key. After turning on, release Vol- key.
Download: http://1drv.ms/1VG4wmt
P.S. You need the latest version of WinRAR;
My bet - missing drivers and USB boot. What device was source of Win10 IoT?
When Win10 for RPi2 was announced I thought about trying the same... sadly I don't own RT device anymore. But as it started booting, seems that secureboot certs are still valid
Dj_Art said:
I tried to run Windows 10 IoT from RPi2 on the Surface RT with included drivers from Surface RT. Appears BDOS error CRITICAL_PROCESS_DIED. Maybe someone will change something? To run the system, unpack the archive on the USB-stick formatted in FAT32.
For launch on Surface RT, turn off the device, hold Vol- and press Power key. After turning on, release Vol- key.
Download: http://1drv.ms/1VG4wmt
P.S. You need the latest version of WinRAR;
Click to expand...
Click to collapse
It is possible to run it, https://twitter.com/never_released/status/660133493872140288 (it's me)
That is fantastic! How were you able to do so, where others have failed?
black_blob said:
It is possible to run it, https://twitter.com/never_released/status/660133493872140288 (it's me)
Click to expand...
Click to collapse
hilga007 said:
That is fantastic! How were you able to do so, where others have failed?
Click to expand...
Click to collapse
I just installed the RPI image without modifications in a USB stick, after adding the Kits Secure Boot policy to fool Win10IoT
I wonder if it's possible to get Windows 10 Mobile executables to run?
SilverHedgehog said:
I wonder if it's possible to get Windows 10 Mobile executables to run?
Click to expand...
Click to collapse
Check the link to the picture posted above. The answer there is
' potentially yes' -
Would be awesome btw..
P.S. You need the latest version of WinRAR;[/QUOTE]
You can actually install Windows IoT on any x86 tablet, like new surface or the ridiculously cheap Linx1010. On BayTrail tablets you can usually boot the minnowboard image and install all the drivers. For Apollo Lake you have to build your own image of Windows IoT because Microsoft does not provide x64 images, and most computer have 64-bit UEFI.
Check out my guide for detail, i can't post URIs here, but it's blog.quickbird run-windows-iot-everywhere (google that)
If I want to flash Win10 IoT instead of running off of USB, what would I need to do?
Edit: Nevermind -- I saw the youtube video. Anyone know the status on Redstone?
Any update on this? Would love for it to work
I have a Windows RT tablet. I successfully performed downgrade from 8.1 to 8.0. The former owner when sat on Windows 8.1 RT said that he was not updated. That's nice. After creating the second user, I started trying to perform secureboot debug. In the account policy I created another user and assigned to him all the roles, including administrator, User Replicator, etc. After that I managed to run the script and on a black background to press the treasured inscription "Accept and install". After the download, I ran the command that was in the Readme file from the Secureboot folder. After that I started to prepare a flash drive. Build ffu file Windows 10 IoT as a person from the video I mounted through the command DISM /mount-ffu. After that I added the files efi to download, but unfortunately further I did not succeed in doing anything. By the way I install a jailbreak. When you try to boot from a prepared SD card, it ignores it. All the methods are tried. What could be wrong? i may to record video
I successfully installed Windows 10 iot core on Surface RT! And I need help for install drivers!!!!
mickel52 said:
I successfully installed Windows 10 iot core on Surface RT! And I need help for install drivers!!!!
Click to expand...
Click to collapse
How were you able to do it, Could you explain? I have an old RT sitting around and I cant do anything with it.
I haven't been able to find a definitive answer as the official guide that @jcase and @beaups put out references PC but not mac or linux. It appears that depixel8 is a script and not a windows .exe file, so maybe i can use my linux laptop...? Anyone have experience unlocking the VZW Pixel bootloader using depixel8 on a Linux machine?
(I just got the Pixel and dont want to repeat what happened with my VZW S4 bootloader being perma -locked)
I used a PC, but there's no reason you can't use a linux machine, you're just using it to copy a file and run a few commands via adb, dePixel8 runs on the phone. Get adb and fastboot set up and you're good to go.
jjlangen said:
I used a PC, but there's no reason you can't use a linux machine, you're just using it to copy a file and run a few commands via adb, dePixel8 runs on the phone. Get adb and fastboot set up and you're good to go.
Click to expand...
Click to collapse
That's what i figured. Thanks for chiming in.
sokrboot said:
I haven't been able to find a definitive answer as the official guide that @jcase and @beaups put out references PC but not mac or linux. It appears that depixel8 is a script and not a windows .exe file, so maybe i can use my linux laptop...? Anyone have experience unlocking the VZW Pixel bootloader using depixel8 on a Linux machine?
(I just got the Pixel and dont want to repeat what happened with my VZW S4 bootloader being perma -locked)
Click to expand...
Click to collapse
A Mac and a Linux box are still PCs. PC = Personal Computer
jcase said:
A Mac and a Linux box are still PCs. PC = Personal Computer
Click to expand...
Click to collapse
Thanks, in my haste and uncaffeinated state my original post and/or title was poorly worded. My confusion wasn't about what is or isn't a PC but whether or not I was correct about dePixel8 not being a windows 'exe' file. I was on mobile at the time and couldn't tell exactly what kind of file I'd be dealing with, so was just looking for a bit of reassurance.
I appreciate the work you do for the Android community. A small donation for you and the March of Dimes(?) is forthcoming.
sokrboot said:
Thanks, in my haste and uncaffeinated state my original post and/or title was poorly worded. My confusion wasn't about what is or isn't a PC but whether or not I was correct about dePixel8 not being a windows 'exe' file. I was on mobile at the time and couldn't tell exactly what kind of file I'd be dealing with, so was just looking for a bit of reassurance.
I appreciate the work you do for the Android community. A small donation for you and the March of Dimes(?) is forthcoming.
Click to expand...
Click to collapse
Ya it runs on the phone
Please direct all donations to make a wish
I've been informed that this secure boot unlock is only for Windows 8.0 and NOT 8.1. Attempting this on Windows 8.1 can result in a brick! This may also be risky for Windows 8.0 You've been warned.
We need some serious help and organization. This thread will be dedicated to getting Linux on these Surface RT tablets. We already have the secure boot unlock so why don't we have a full Linux install? I believe it's because all the information is strewn about the internet with incomplete information and broken links. So please keep this thread topic only on the topic of secure boot unlock and Linux booting on Surface RT.
Ok so about the unlock, for those who are asking you can get it here, check the end of the post. To run the secure boot unlock: Move the SecureBoot zip to the desktop, unpack it, and run the script InstallPolicy.cmd as an administrator. (right click and "run as administrator"). In my case it was not working properly because I was trying to run it off a removable usb thumb drive, you should run it from the desktop. Your tablet should reboot then you should get the "secure boot debug policy applicator" install menu with a bunch of warning text. If your RT device has a removable keyboard then please use the volume keys as the "arrow keys" to select accept and confirm it by taping the "windows key" below the screen, I had to do that for my Surface RT. It now should reboot back to windows and at this point you'll want to open a CMD in administrator mode (search for CMD, right click and "run as administrator") and run the command as mentioned in the included readme file.
Code:
bcdedit /set {default} testsigning on && bcdedit /set {bootmgr} testsigning on
Now reboot one last time and your good.
So now what? How do you boot? You can boot anything now by going to settings in the side bar menu, clicking "change PC settings", navigating to "general" settings, and at the bottom of that you should see an "advanced startup". Selecting "restart now" underneath "advanced startup" should bring you to a menu that will allow you to select a USB drive to boot off of. Included at the bottom is also a grub bootloader that's been created for these RT devices and a couple of other possibly related zips.
WE NEED PEOPLE WORKING ON GETTING THE KERNEL TO BOOT! SHARE THIS TO ANYONE YOU KNOW WHO COULD HELP! I was trying to use the source for a related (but not totally the same) hardware known as the "Cardhu Development Board" from Nvidia. The source code for that can be found here, and their own released version of Ubuntu Linux for Cardhu can be found here. I couldn't get the compiled kernel from source to boot but maybe some drivers can be had from that repository.
I DID NOT CREATE ANY OF THESE HACKS, I'm just more a hobbyist learning computers and programming who also loves Linux. Credit seems to go to users @Wack0Distractor, @black_blob, and the folks at ROL for the original hacks. Credit goes to @[email protected]@f for recovering the files, his original post is here, seems ROL had a bit of a issue and a lot was lost but their IRC is still up.
List of possibly related and useful information
Secure Boot Golden Keys: https://web.archive.org/web/20170604013028/https://rol.im/securegoldenkeyboot/
Below is a index of posts in this thread that should be of interest.
Page 9 Post #85 -- Getting into APX mode (AKA RCM mode): https://forum.xda-developers.com/showpost.php?p=77286176&postcount=85
Reserved #2
How do we use the GRUB, ci_tools_arm & EFIESP??
I have Windows RT 8.1
XDA-00 said:
How do we use the GRUB, ci_tools_arm & EFIESP??
I have Windows RT 8.1
Click to expand...
Click to collapse
My Surface RT was a used tablet and it came with Windows 8.0 afaik, so everything just worked. I actually don't know what "ci_tools_arm" are but I do know with EFIESP and GRUB you just unzip the contents of just one (take your pick) to the root of a USB drive and they will boot whatever you configure them to boot. "EFIESP" can be used to boot the Windows IOT from https://forum.xda-developers.com/wi...ows-phone-windows-10-mobile-surface-t3365743/ while GRUB can be used to boot ANYTHING, even Windows, so long as you have the proper kernel or files. If you try to boot GRUB you'll just get the GRUB loader screen and the attachable keyboard doesn't work in GRUB, a USB keyboard might though. Right now we need someone to compile a working kernel with drivers for the RT line of devices.
EDIT: Booting stuff requires that you unlocked "secure boot" as mentioned above.
ShapeShifter499 said:
Reserved
Click to expand...
Click to collapse
You are going to get people bricked with this method.
DO NOT under any circumstance use this guide if you are on RT 8.1. It will end up in crashing your device and possibly even bricking it (that has been reported). RT 8.1 automatically relocks the secure boot and if you try and install the EFI, it will brick your device.
DO NOT follow this guide unless you are on RT 8.0. Even if you are on RT 8.0, it is still risky.
The kernel for RT is structured differently than a standard linux ARM kernel. That's one of the reasons why linux will most likely not happen for RT devices.
Sent from my Q5 using XDA Free mobile app
Is there any way to revert to RT 8 from 8.1?
2390 said:
Is there any way to revert to RT 8 from 8.1?
Click to expand...
Click to collapse
Nope
Sent from my Q5 using XDA Free mobile app
Qiangong2 said:
You are going to get people bricked with this method.
DO NOT under any circumstance use this guide if you are on RT 8.1. It will end up in crashing your device and possibly even bricking it (that has been reported). RT 8.1 automatically relocks the secure boot and if you try and install the EFI, it will brick your device.
DO NOT follow this guide unless you are on RT 8.0. Even if you are on RT 8.0, it is still risky.
The kernel for RT is structured differently than a standard linux ARM kernel. That's one of the reasons why linux will most likely not happen for RT devices.
Sent from my Q5 using XDA Free mobile app
Click to expand...
Click to collapse
Added warning to op. Thank you for letting me know.
Qiangong2 said:
You are going to get people bricked with this method.
DO NOT under any circumstance use this guide if you are on RT 8.1. It will end up in crashing your device and possibly even bricking it (that has been reported). RT 8.1 automatically relocks the secure boot and if you try and install the EFI, it will brick your device.
DO NOT follow this guide unless you are on RT 8.0. Even if you are on RT 8.0, it is still risky.
Click to expand...
Click to collapse
Quit the fearmongering, MSFT's security update has already been worked around
The kernel for RT is structured differently than a standard linux ARM kernel. That's one of the reasons why linux will most likely not happen for RT devices.
Click to expand...
Click to collapse
What do you mean by this
Sam Za Nemesis said:
Quit the fearmongering, MSFT's security update has already been worked around
Click to expand...
Click to collapse
The new dev tool, when run together with unlocking secure boot, bricks your device.
What do you mean by this
Click to expand...
Click to collapse
The ARM processor is configured to the NT kernel. Unlike most which are configured to a Unix kernel.
Sent from my Q5 using XDA Free mobile app
Qiangong2 said:
The kernel for RT is structured differently than a standard linux ARM kernel. That's one of the reasons why linux will most likely not happen for RT devices.
Click to expand...
Click to collapse
Isn't the device not loading any kernel when GRUB is loaded on a Surface RT? I thought when GRUB was proven to load, that any kernel would load on the Tegra processor, I've seen documentation online where most of the Tegra code (from Nvidia or from Open Source) was ported into the latest Linux kernel.
ShapeShifter499 said:
Isn't the device not loading any kernel when GRUB is loaded on a Surface RT? I thought when GRUB was proven to load, that any kernel would load on the Tegra processor, I've seen documentation online where most of the Tegra code (from Nvidia or from Open Source) was ported into the latest Linux kernel.
Click to expand...
Click to collapse
We could just adapt a Linux kernel (like with Android) if the RT kernel was a Linux kernel, but it isn't. RT blocks different kernels from being loaded (like a locked bootloader, just more complex)
Sent from my Q5 using XDA Free mobile app
Qiangong2 said:
We could just adapt a Linux kernel (like with Android) if the RT kernel was a Linux kernel, but it isn't. RT blocks different kernels from being loaded (like a locked bootloader, just more complex)
Sent from my Q5 using XDA Free mobile app
Click to expand...
Click to collapse
Is there any documentation stating this? Is the RT kernel active when we boot up GRUB?
There is Linux (Android) kernel available for TF502T Asus tablet which is almost the same as Surface RT and totally same as TF600T. Here you can still download it from Asus website: https://www.asus.com/us/support/Download/28/1/0/17/32/
[email protected]@f said:
There is Linux (Android) kernel available for TF502T Asus tablet which is almost the same as Surface RT and totally same as TF600T. Here you can still download it from Asus website: https://www.asus.com/us/support/Download/28/1/0/17/32/
Click to expand...
Click to collapse
I could give it a shot later, sure. Thanks for the information.
ShapeShifter499 said:
Is there any documentation stating this? Is the RT kernel active when we boot up GRUB?
Click to expand...
Click to collapse
We have restricted access (basically cannot do anything), but yes. It is active.
Sent from my Q5 using XDA Free mobile app
Qiangong2 said:
We have restricted access (basically cannot do anything), but yes. It is active.
Sent from my Q5 using XDA Free mobile app
Click to expand...
Click to collapse
I'm guessing there is no known button combo to boot up some sort of debug mode, like the fastboot mode on android devices.
Has anyone seen if there are any JTAG or serial connections somewhere on the board?
ShapeShifter499 said:
I'm guessing there is no known button combo to boot up some sort of debug mode, like the fastboot mode on android devices.
Has anyone seen if there are any JTAG or serial connections somewhere on the board?
Click to expand...
Click to collapse
Not as far as I know
Sent from my Q5 using XDA Free mobile app
Qiangong2 said:
Not as far as I know
Sent from my Q5 using XDA Free mobile app
Click to expand...
Click to collapse
Microsoft has really screwed this tablet then, I'm out of ideas for now. For anyone coming across this, if you have ideas or possible solutions please share them.
Hi all,
On Android 13, Google enabled KVM support for Tensor Chips model(Pixel 6 / 6pro / 6a). So we can run a Virtual machine at full speed, but there is no APP to utilize this feature.
I modified the Limbo Emulator (QEMU), so it can enable the KVM on Pixel 6 Phones. Due to the limitation of the kernel, the APP needs ROOT permission to access the KVM service(/dev/kvm)
Currently, only VNC is working on this APP, and you can only boot directly using the Linux kernel. UEFI did not work on KVM.
Network functions worked, but you may need to set the DNS inside the Guest OS.
Arch Linux for arm64 runs pretty well on Limbo. It runs even faster than Raspi 4. You can download it from ArchLinuxARM-aarch64-latest.tar.gz
Other Linux can also run on the Limbo, but you may need to recompile the kernel to enable virto-related functions.
See https://forum.xda-developers.com/t/...th-kvm-acceleration-for-tensor-chips.4501665/
this works without kvm, but windows 10 not starting
lentas said:
this works without kvm, but windows 10 not starting
Click to expand...
Click to collapse
windows requires uefi whether its the arm variant or not. I have windows 11 for arm on my surface duo. requires a custom uefi boot
TechX1991 said:
windows requires uefi whether its the arm variant or not. I have windows 11 for arm on my surface duo. requires a custom uefi boot
Click to expand...
Click to collapse
it still dont work
lentas said:
it still dont work
Click to expand...
Click to collapse
Have you written a custom uefi boot, and Windows still doesn't boot?
it gets "loading files" and then screen is black
lentas said:
it gets "loading files" and then screen is black
Click to expand...
Click to collapse
also requires drivers and such for like the soc, graphics chip, etc. On the surface duo 1, charging while booted to windows doesn't work
@wasdwasd0105 I would like you to share how you created the PFlash image for UEFI. specifically how you bypass the error with kvm_set_user_memory_region. I do have an idea on how to get RAMFB to work, but I can't seem to find how to fix that particular issue.
coreycusick said:
@wasdwasd0105 I would like you to share how you created the PFlash image for UEFI. specifically how you bypass the error with kvm_set_user_memory_region. I do have an idea on how to get RAMFB to work, but I can't seem to find how to fix that particular issue.
Click to expand...
Click to collapse
add my discord wasdwasd0105#2283