Related
Hi
I want to transfer my own windows ce 6.0 os design to a htc prophet ?
Is it possible?
I found a nk.bin file in os release dir. is it the same as nk.nbf or it needs something to be added to it like ipl/spl?
No.
Let me just verify that I understand you correctly:
You have Platform Builder for Windows CE (not Mobile) 6 and you compiled and OS.
Now you want to put it on your Prophet?
Here is why this can not work:
a) You do not have the hardware drivers. Even if by some miracle you got the Prophet BSP (board support package) from HTC, because CE 6 architecture is so different from CE 5 on which the BSP is based you would have to rewrite them.
b) The nk.bin Platform Builder produces is in plain binary format. The nk.nbf which the Prophet bootloader can recognize is in HTC's special encrypted format so the bootloader will not read the bin.
Yes. You get it right. I know if I want to use phone features completely I need BSP. But what if I want just use some standard features? just LCD and phone features.
Also I saw nbftool that decrypt and encrypt nbf files. Can I use it to encrypt files for prophet?
You need BSP for everything, not just "full features". Every little bit of hardware that connects to the CPU requires a driver unique for your device, that includes the screen, the digitizer (touch screen), hardware keys, USB port, SD card, etc.
This is why the Linux project for these devices hasn't moved beyond booting the kernel.
There are tons of work to be done (not to say it is impossible).
I am not sure about the nbftool but even if you manage to create an image that boots best case scenario is you will see something on the screen.
But you will have no way of controlling the device - no touch screen or keys, and no way to connect to it from windows since you do not have USB drivers.
Then what are the BSPs which exist in Wince by default. There is a ARMv4. How can I use it? Can you help me?
There is ARMv4 and there is Samsung, TI, Xscale, etc. Unlike x86 - all are different. Different memory map, different GPIO, different periferials.
Better waste your time on something else. Anyway CE 6 does not have phone features at all. Compile it for your PC and see that yourself.
mamaich said:
There is ARMv4 and there is Samsung, TI, Xscale, etc. Unlike x86 - all are different. Different memory map, different GPIO, different periferials.
Better waste your time on something else. Anyway CE 6 does not have phone features at all. Compile it for your PC and see that yourself.
Click to expand...
Click to collapse
I think ARMv4 BSP in Platform Builder already have enough driver for this type of CPUs. And HTC phones are ARMv4. So normaly I should be able to build and transfer my OS to there. CE 6 have buitin drivers for modem,LCD and so on. But there is no phone. Because phone is an app that runs on CE. So if I just want to use devices like modem It is enough. The problem is nbf files ae encrypted and os.bin file should encrypt to os.nb and then transfer to device.
shariat said:
I think ARMv4 BSP in Platform Builder already have enough driver for this type of CPUs. And HTC phones are ARMv4. So normaly I should be able to build and transfer my OS to there. CE 6 have buitin drivers for modem,LCD and so on. But there is no phone. Because phone is an app that runs on CE. So if I just want to use devices like modem It is enough. The problem is nbf files ae encrypted and os.bin file should encrypt to os.nb and then transfer to device.
Click to expand...
Click to collapse
you dont really understand the problem.
ARMv4 is not a cpu, it is the ARM version 4 instruction set ....
afaik your phone has some kind of OMAP.
i don't know if CE6 has a BSP for that, but even if it does, it will still not work without modifications.
a recent example. a friend of mine wanted to download a generix xscale 25x eboot (bootloader) to a device that had xscale 255. he almost killed the whole device because the RAM memory map of this generic eboot managed to overlap with the device's original bootloader memory space in ROM. (the virtual memory mapping differed in such an unlucky way.) and so the device's own bootloader thought it had to flash it in instead of loading it into RAM and it overwrote part of itself. luckily only the splashscreen got damaged...
(and of course the device would not boot this eboot.)
that's what happens when someone who has not ever dealt with hardware and memory mappings (i.e. you) tries to play with platform builder and flashing.
also, what is this about CE6 having built in drivers for the modem (you mean GPRS?) and LCD. it doesn't have the correct ones for your device.
and, the phone is more than just an app, it also needs drivers. the modem needs it too.
all in all...i strongly discourage you trying to flash that nk.bin.
it is not even in a format that your bootloader will understand, it is MS BIN format. the nk.nb0 in same release dir (or if there is none then cvrtbin will convert it) will be the raw format that needs to be encoded for nbf, but that is far from enough because it will never boot anyway. so forget this info.
cmonex said:
you dont really understand the problem.
ARMv4 is not a cpu, it is the ARM version 4 instruction set ....
afaik your phone has some kind of OMAP.
i don't know if CE6 has a BSP for that, but even if it does, it will still not work without modifications.
Click to expand...
Click to collapse
But at least the way of using loader is possible. Like how Linux is loaded
shariat said:
But at least the way of using loader is possible. Like how Linux is loaded
Click to expand...
Click to collapse
loader, for what purpose?
cmonex said:
loader, for what purpose?
Click to expand...
Click to collapse
For running WinCE , like Linux. Am i right? Linux devs uses Loader to load Linux on Mobile devices. I think I am confused. Help me on this. My purpose is to use my own OS design.
shariat said:
For running WinCE , like Linux. Am i right? Linux devs uses Loader to load Linux on Mobile devices. I think I am confused. Help me on this. My purpose is to use my own OS design.
Click to expand...
Click to collapse
well, for linux, the drivers have to be written too. (most of the time there are existing ones with source available that can be modified, though.)
so it is more complicated than that.
shariat: writing your own OS for this hardware is not impossible, but is not easy.
I suggest you go away for a while and get hold of platform builder and an arm reference guide and read everything you can about the device, the memory structure, your dedicated hardware structure, and then start writing.
Knowing how the hardware and CPU operate is fundamental to the OS you will write. Platform Builder will give you some source code access and help give you some ideas.
This is a nearly impossible task for a hobbyist coder. I'm sure people will help you, but you need to discuss what you have in mind.
Have a look here for some other easier ideas:
http://simpleos.iroot.ca/index.php
V
OP News: (27.4.2011)
Added Developer Files in case someone acctualy wants to take a look at the Source Code from mamaich. See Post Nr. 5
Older News:
There is still alot of Information yet to be Organized and published but feel free to submit Links, Drivers, Addons, Plugins, or anything else you found and tested. Just always remember never to publish any licensed stuff.
Some Cool stuff some XDA Members have already tested: Photoshop 4.0, 3D Max v3.1, ZBrush2, SiSoft Sandra 2000, OpenOffice, Virtual Joystick, etc.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Rules & Reminders:
- Always respect XDA-Developers.com Forum Rules!
- Please try to stay on Topic as much as possible.
- Do not post any Copyrighted Material without explicit and written permission of the copyright owner. If you own a legitimate License this Thread will show you everything you need to know to recycle that license to create your own Windows Mobile Device Images.
- Hopefully this Thread will stay impartial to any Device but that said having a 1Ghz Snapdragon does not hurt.
- There is allot of Information to be collected, verified, and compacted. Any help is greatly appreciated and rewarded by special mentionings throught this Thread. PM Swiss420 with suggestions, feedback, ideas, or basically any material that you think could be usefull for the thread.
- Use the Thanks Button instead of posting "thanks" and please don’t ask why we are rolling this up again. We know its old news but I am sure we can provide new insights and focus the Information. No! Networking has not been achieved yet. But as we see it, it is a Question of what was first the Chicken or the Egg.
[QEMU Applications]
QEMU v0.91 [/Storage Card/QEMU] --> Download
Qemu Manager v7.0 (April 2010) with Qemu 0.11.1 and KQEMU Support -> Download
Qemu Manager v6.0 (April 2009) with Qemu 0.10.2 and KQEMU Support -> Download
Qemu Manager v5.0 (Feb 2008) with Qemu 0.9.0/0.9.1 and KQEMU Support -> Download
Qemu Manager Version 4.0 (Feb 2007) With QEMU 0.9.0 and KQEMU support -> Download
3D_Toolbar_V1.qtb
3D_Toolbar_V2.qtb
3D_Toolbar_V3.qtb
3ddesktop.qtb
boot_Toolbar.qtb
BOOT3D.qtb
FULL.qtb
full_keyboard.qtb
toolbar-boot.qtb
toolbar-Desktop.qtb
toolbar-full.qtb
toolbar-fullO.qtb
toolbar-her.qtb
toolbar-min.qtb
Attached is a preliminary Version of QEMU Extended and preped for Windows 98SE by aSiD1712 and contributing work by TruckyBN. See Original Thread -->
[QEMU Plugins]
int33mouse.dll [missing Description]
int21hk.dll [missing Description]
heroes2.dll [missing Description]
FMOD.DLL [missing Description]
LIBUSB0.DLL [missing Description]
SDL.DLL [missing Description]
[QEMU Settings]
[Screenshot QEMU Manager running Windows 98SE]
Code:
CMDLINE.TXT
-tb-size
8
-emul
\Storage Card\QEMU\emul\WinXX
[QEMU Information]
QEMU is a generic and open source machine emulator and virtualizer.
When used as a machine emulator, QEMU can run OSes and programs made for one machine (e.g. an ARM board) on a different machine (e.g. your own PC). Or viceversa. By using dynamic translation, it achieves very good performance.
In order for QEMU to run under Windows Mobile it was necessary to recompile the OpenSource Code. Mainly mamaich at pdaprime.com has taken on this task himself in 2004 and succesfully recompiled QEMU. Unfortunately in March 2010 Mamaich announced the following:
"I've stopped working on QEMU and HOMM 1-2 ports for WinMobile. Earlier I've published complete source code and a toolchain used to build QEMU, but links were lost after this forum have crashed. I'll look for them and reupload in a few days. Currently I'm attaching source code for launcher and all plugins. To build them you'll need Visual Studio 2008. To build QEMU you'll need cygwin, my GCC 3.3.3 port (a bit modified for QEMU), i'll upload them after I'll find them.
Edited:
Added toolbar editor with sources. To compile - use C++ Builder. Usage is similar to DosBox TB editor.
Edited:
Added compiler (arm-wince-pe-gcc.rar). Extract it to /usr/ directiory of CygWin installation and add /usr/local/arm-wince-pe/bin/ to the start of CygWin $path. This GCC is already preconfigured for QEMU, it contains all needed libs like SDL. Added qemu src (qemu-0.9.1.rar). It is already "./configure"d, just use "make" to build in CygWin environment. Normally QEMU.EXE file should not be modified at all. Everything is controllable from plugins."
March 2010 Mamaich (pdaprime.ru)
Click to expand...
Click to collapse
So were does that leaves us? First off we want to thank mamaich for the great work he has done and wish him all the best. We are putting this together in order to search for someone else with enough knowledge to recompile QEMU and add Network functionality if possible. Hopefully someone steps up to the plate and cracks this nut. He will be able to completly rely on our help in any way shape or form. We will post any Developer Information mamaich has provided at PDAPrime as soon as possible but we would like to check first with mamaich and or pdaprime. For now you can find the allot of the Information here
Original Developer Files from Mamaich (Ad Free xda-developers.ch Links):
arm_wince_pe_gcc.rar (Compiler)
GEN_Toolbar.rar ()
qemu_0.9.1.rar
ui_and_launcher.rar
Download here
This is only a quick overview. We will create Step by Step Instructions for you to follow eventually.
1. Create an Image - use the following command using the qemu-img.exe provided in the QEMU v0.91 [qemu-img create image.img 1000MB] (Creates a Unformated 1Gb Image)
2. Install OS using QEMU Manager for Windows. -> Download here
3. Copy QEMU to SD Card -> Download Example
4. Adjust CMDLINE.TXT, EMUL_CMDLINE.TXT, emul_ini.txt and plugins_ini.txt according to your specific OS and Environment
5. Add a Second Drive by creating a new Image and adding files with WinImage or create a ISO with Nero and load it as a CD Image in QEMU Manager.
6. For debugging and Errors please check the output in: QEMU_OUT.TXT [Error Log]
[QEMU Links]
XDA-Developers Links:
[QEMU on himalayas]
[Windows 95 on HD2]
Offsite Links:
http://en.wikipedia.org/wiki/QEMU [QEMU @ wikipedia.org]
http://wiki.qemu.org/ [QEMU Wiki]
http://www.davereyn.co.uk/ [Home of QEMU Manager]
http://forum.pdaprime.ru/index.php?showtopic=45356&st=240 [Original Thread from mamaich]
http://www.qemu.com/ [QEMU git repositories]
YouTube Videos:
Windows 95 on a HD2 [Swiss420]
Developer Links:
Bug in qemu 0.9.1 (and maybe later) + fix [mamaich @ QEMU Forum]
VBEMP x86 Project - Universal VESA/VBE Video Display Driver [Bearwindows and AnaPa Corporation]
[QEMU Drivers]
[Verified Drivers: These Drivers have been tested and as working classified]
Drivers for Cirrus GD-5446 video adapter
"None available"
Drivers for Realtek 8029AS network adapter (for other OSes try NE2000 compatible driver)
"None available"
Drivers for Realtek 8139 network adapter
"None available"
Drivers for Sound Blaster 16 adapter"
None available"
[Caution: These Drivers have not been tested yet: Use and try at your own Risk - Leave Feedback with exact file name]
Drivers for Cirrus GD-5446 video adapter
DOS Drivers
OS/2 Drivers
Windows 3.1, Windows NT and Windows 9x Drivers
Drivers for X.Org and X11 are inside "cirrus" module.
QNX includes the driver.
Drivers for Realtek 8029AS network adapter (for other OSes try NE2000 compatible driver)
BeOS R4 and R4.5 instructions (Use NE2000 PCI)
BeOS R5 instructions (Use NE2000 PCI)
DOS driver for NDIS2
LANtastic 4 driver
LANtastic 5 driver
Windows NT 3.51 driver
Windows NT 4.0 driver
Novell NetWare Client32 driver
Novell NetWare Client for DOS ODI driver
Novell NetWare Client for OS/2 ODI driver
Novell NetWare Server driver
OS/2 driver for NDIS2
SCO UNIX driver
UNIXWare driver
Windows for Workgroups driver (3.1 and 3.11)
Windows 95 driver
Windows 98 driver
Windows 2000 driver
Windows XP includes driver
Windows Vista stopped support
Linux driver is in ne2k-pci.c
Drivers for Realtek 8139 network adapter
BeOS R4 and R4.5 driver
BeOS R5 driver
DOS driver for NDIS2
FreeBSD driver (for versions that do not include it in kernel repository)
JavaOS driver
MacOS 8.5, 8.6, 9.0 and 9.1 driver
Novell NetWare Client32 driver
Novell NetWare Client for DOS ODI driver
Novell NetWare Client for OS/2 ODI driver
Novell NetWare Server (from 3.12 onward)
SCO UNIX driver
Slackware Linux 8 driver
Solaris 7, 8, 9, and 10 driver
UNIXWare driver
VXWorks for x86 driver
Windows NT 3.51 driver
Windows NT 4.0 driver
Embedded Windows NT 4.0 driver
Windows for Workgroups driver (3.1 and 3.11)
Windows 95 driver
Windows 98 driver
Windows 98 Second Edition, Windows Me and Windows 2000 driver
Windows XP and Windows XP Professional x64 Edition driver
Windows CE 2.0 for x86 driver
Windows CE 3.0 for x86 driver
Mac OS X 10.0.4 and Darwin/PPC 1.3.1 driver
Mac OS X 10.1, Darwin/PPC 1.4.1 and Darwin/PPC 5 driver
Mac OS X 10.2 and Darwin/PPC 6 driver
Linux driver is in 8139too.c or 8139cp.c
Windows Vista, Windows 2003 and Windows CE.NET include drivers
Drivers for Sound Blaster 16 adapter
DOS driver
Windows NT 4.0 driver
Windows 95 and Windows 98 driver
OSS and ALSA have drivers.
Windows 98 SE, Windows Me, Windows 2000, Windows XP and Windows 2003 include drivers.
Windows Vista dropped support.
[DOS & Windows 3.1 for QEMU]
Reserved for Windows 3.1
[Windows 95 for QEMU]
Windows 95 osr2
Graphics: Cirrus Logic 5446 PCI v1.41
Network: [Not yet Available]
Sound: Creative Labs Sound Blaster 16 or AWE-32
Hard disk controllers: Intel 82371SB PCI Bus Master IDE Controller
Monitor: (Unknown)
Mouse: (Unknown)
Ports (COM & LPT): COM1 / LPT1
System Devices: (Unknown)
Videos:
Windows 95 on HD2 [by Swiss420]
Screenshots: 1
[PDAPrime Thread]
Mamaich [pdaprime], aSiD1712 [xda-developers], TruckyBN [xda-developers]
[Windows 98 for QEMU]
Reserved for Windows 98 Ori.
[QEMU for Windows 98SE]
Windows 98 Second Edition
Videos:
"None yet"
Screenshots: 1 2
Windows NT 4.0 for QEMU
Reserved for Windows NT 4.0
[Windows ME for QEMU]
Reserved for Windows ME
[Windows 2000 for QEMU]
Reserved for Windows 2000
[Windows XP for QEMU]
Reserved for Windows XP
[Windows 7 for QEMU]
Reserved for Windows 7
Linux Builds
There are many Open Source Operating Systems that run great under QEMU for Windows Mobile. Here you will find a few that have been reported as Working.
--------------------
Puppy Linux / Linux
Puppy Linux is a special build of Linux meant to make computing easy and fast
--------------------
Icaros Desktop light / pre-configured AROS Desktop Environment / AmigaOS 3.1 / Fast and Stable
Icaros Desktop is a pre-configured AROS desktop environment for the PC platform, distributed on a bootable live media. The AROS Research Operating System is a open source lightweight, efficient and flexible desktop operating system, aiming at being compatible with AmigaOS 3.1 at the API level, while improving on it in many areas. [Supports Amiga Forever and AMIGA Games - Untested - Please Report findings]
First
Great work mate!
I think this will be going to an big Thread!
Greetz Tokl
Looks like a very interesting thread I downloaded the QEMU.7z file and transfered it to my phone, but without a base OS, I doubt it'll work. I think I have a 95 disk laying around here somewhere. How would I go about emulating it? Those posts only have images of download links, no actual links
BarrettBear said:
Looks like a very interesting thread I downloaded the QEMU.7z file and transfered it to my phone, but without a base OS, I doubt it'll work. I think I have a 95 disk laying around here somewhere. How would I go about emulating it? Those posts only have images of download links, no actual links
Click to expand...
Click to collapse
Yes you are right the acctual instructions are not yet published. But to get you jumpstarted just download QEMU Manager for Windows here use that to install your Windows 95 or 98 and transfer the image to the SDCard. Will send you a IM with some more information. Feel free to ask if you get stuck same goes for everyone else.
2/18 Update:
USB charging and controller works, audio probably works. Here's some update on this project:
Battery
Put C:\DPP and C:\EFIESP back. Nokia's driver reads C:\EFIESP\Battery.json in kernel mode (WTF). If you have NokiaEnergyDriver.sys and other PMIC/PEP/MIPI BIF (on some models) drivers installed, you should get battery show up.
Sign drivers?
Yes. Sign everything to prevent bad things from happening. I used a commercial certificate for conveience , but you don't have to do that. Here's a handy script that generates a self-signed certificate and installs it on your phone: https://gist.github.com/imbushuo/4de89ad18a0f538d8ebd18bf6daca56a
Download it, run it as administrator and specify ImageDir to your phone's partition (in mass storage mode). Then sign all your drivers binaries (and catalogs as well) with the fingerprint provided.
When signing your drivers, remember timpstamp all drivers. DigiCert's help documentation is useful for signing binaries.
Turn off UMCI
See https://forum.xda-developers.com/showpost.php?p=36394268&postcount=222. Set UMCIAuditMode key to allow all desktop applications and UMDF drivers load.
Make USB work
You will need several supplemental drivers from Windows Phone: BattFltr.sys, CAD.sys, ufx01000.sys, ufxsynposys.sys (or ufxchipidea.sys, depends on your chipset). Copy registry keys (HKLM\ControlSet001\Services and HKLM\ControlSet001\Enum\ROOT\CAD / HKLM\ControlSet001\Enum\ROOT\BattFltr) add supplemental WDF registry keys. Some files are attached as attachments, so you can take a look to get some idea about that.
Make Windows Store Apps work on unsupported resolution
See my blog post.
---------
While this project is not totally finished (e.g. No Battery status/charging unknown, no cellular, no audio), I decided to post this thread as many people asked me about the tutorial. This is just a brief tutorial, you need to have plenty of time on this to make this happen. Be careful as some steps are very dangerous.
This tutorial is provided AS-IS, without any implicit or expressed warranties. By reading this brief tutorial, you are agreed that you are taking your own risk trying this. I am not responsible for any possible consequences of installing Windows RT or other non-Windows Phone OS on Lumia phones. If your phone ships with Windows 10 Mobile, then this tutorial might not fit you. You can try drivers from other models, but I have no guarantee on this.
General workflow
- Unlock your phone with WPInternals 2.4
- Enter mass storage mode, copy registry files from MainOS partition
- Copy files from DPP partition
- Download Windows RT 8.1 ISO (publicly available on Internet, Google it)
- Download a Lumia 2520 recovery image for some files (I will post these files later)
- Download a Windows Phone 8.1 firmware for your phone
- Extract drivers, re-assembly INF files
- Patch some drivers (see my note)
- Self-sign some drivers (see my note)
- Make sure you know what you are doing: Delete MainOS and Data partition, create new NTFS partition for Windows RT. Do not touch other partitions.
- Apply system image (dism works fine)
- Copy DPP files back (C:\DPP)
- Modify sysprep tasks (see my note)
- Apply BCD configuration
- Boot
- Let OOBE fail once
- Go to mass storage mode again, mount registry and force OOBE run again
- Have fun
Notes on this project
ACPI
Reading ACPI DSDT table will help you understand your phone architecture. ACPI tables are located in PLAT partition. It is easy to extract them with 7-zip (after converting FFU to VHD). To decompile dsdt.aml, you need to download iASL tool, which is available on Internet.
Certain devices, like touch screen or panel, require other devices have driver loaded and enabled. This is not shown in Qualcomm's ACPI implementation. In my case, I need PEP, PEP 3rd, GPIO, BAM, I2C Device, QMUX, Shared Memory drivers loaded to make touchscreen work. It varies by model.
Re-assembly INF files
Mount SYSTEM registry from your phone or FFU, go to DriverDatabase\DriverPackages\<Some Driver Package>, each key in driver package key matches INF sections respectively. See some driver INF files to get some idea.
Remember to check ControlSet001\Service for additional information if necessary. If you are working on Windows Phone 8.1 firmware, check \Windows\System32\Packages to make sure you've got correct files and registry configs. These files are gzipped.
Patch drivers
Certain drivers read DPP partition for device-specific calibration information. While Qualcomm shares the codebase between Windows RT and Windows Phone, DPP partition is handled differently between platforms. You can search Unicode string "PhoneNT" to determine whether drivers read DPP or not.
To fool drivers think they are living in Windows Phone, you can create another multi-string value in the ProductOptions key. I created a value called "AnotherSuite" and filled "PhoneNT" in. Then I modified all "ProductSuite" Unicode strings in drivers to "AnotherSuite". Remember to re-calculate linker checksum (dependencies) and PE checksum.
This is critical to make wireless (Wi-Fi and Bluetooth) subsystem work.
Graphics
DO NOT use user-mode driver module from WP on Windows RT. The Windows Phone Qualcomm GPU driver does not implement DirectX 9, which is required by Windows desktop. Using WP UM driver will crash DWM.
To correctly enable GPU acceleration, use kernel driver and decoder module from your firmware, and user mode driver from Lumia 2520's recovery image. At least this works on Lumia 640 XL.
Touchscreen
Touchscreen works, however, WP driver reports wrong metric system to Windows RT. To workaround this, modify SYSTEM\TOUCH key, make some value larger than expected. See my value for 640XL in attachment.
Remove some sysprep tasks
Remove BCD and WinRE specialization and generalization tasks from sysprep task definition. OOBE will fail still. Boot to mass storage mode, mount SYSTEM registry, change setup type to 1 (see your current OS for ideas about other values), change program path to oobe\msoobe.exe. You should be able to see normal OOBE then.
BCD and Driver Signing
Test signing should be on. Disabling integrity check is recommended (though documentation says this key is ignored prior to Windows 10). Copy catalogs to the new OS, and self-sign drivers you patched.
Kernel Debugger
To enable WinDbg KD, modify your phone BCD:
Code:
bcdedit /store <Path> /dbgsettings usb TARGETNAME:WOATARGET
bcdedit /store <Path> /set {Your OS GUID} Debug On
Connect your phone to PC, start WinDbg, USB kernel debugging, target name "WOATARGET".
Have fun with Windows RT on Lumia, I am going to continue working on audio and battery
Follow
Ty Imbushuo , GREAT WORK
didnt you forgot to make efiesp guid to a efi partition else bcd cant be updated
Is there a way to patch the kernel or a bypass to avoid SECURITY_SYSTEM BSOD on MSM8960 devices?
Thanks for your work. I hope to get a newer Windows Phone soon and try Win10PE, I'm working on a custom shell that hopefully grants it a good experience on handheld devices since we lack ARMv7 ShellExperiences
J0SH1X said:
didnt you forgot to make efiesp guid to a efi partition else bcd cant be updated
Click to expand...
Click to collapse
Qualcomm's firmware is weird, so I didn't do that. (They hard-coded something) Maybe I will try it later with a dev board and see what will happen.
Fantastic job :good:
Is it possible to enable a second external monitor via Miracast ?
What about bluetooth keyboard and mouse ?
Lumia 950/XL should also support 2x monitors ( DisplayPort/HDMI via USB-C ).
It also has more RAM and might run apps better than L640.
imbushuo said:
Qualcomm's firmware is weird, so I didn't do that. (They hard-coded something) Maybe I will try it later with a dev board and see what will happen.
Click to expand...
Click to collapse
thats weired on my 930 this is NEEDED to get rt to boot but weired enough my 640 lte doesnt boot it at alll but sadly i dont get how to reassamble the inf files (im litterally just comparing my compiled touch driver inf with the registry of my 930)
I can not find the windows rt on the Internet. Can I send the file link download?
imbushuo said:
While this project is not totally finished (e.g. No Battery status/charging unknown, no cellular, no r FFU, go to DriverDatabase\DriverPackages\<Some Driver Package>, each key in driver package key matches INF sections res
Click to expand...
Click to collapse
I use google translate so it's hard to follow, it's great when you have a video tutorial, everything is more intuitive and easy.
INF files Qualcomm ARM-based View attachment Inf.zip
prokakavip said:
I use google translate so it's hard to follow, it's great when you have a video tutorial, everything is more intuitive and easy.
Click to expand...
Click to collapse
If you are an end user I would recommend waiting for WPInternals partition dumps for your device
I knew this solution... so they cant make general Qualcomm drivers never. Device specification is nightmare. Better get a hammer and deepmagic
Thank you for all the effort of going through this and providing the information.
Can somebody whoever upload fixed registry files and drivers? i was able to follow all steps successfully (except these parts) but on first boot i just get a blue screen with a sad smiley.
Also, i assumed you meant applying the install.wim image via DISM from the Windows RT 8.1 ISO.
(For those who need more help with this, Google: "Append, apply, and export volume images with a Windows Image (.wim) file",
i'm not allowed to post links due to post count).
Die Anleitung ist jetzt auch in deutsch verfügbar und hier zu finden:
Windows RT 8.1 auf ein Lumia installieren
WPVision.de said:
Die Anleitung ist jetzt auch in deutsch verfügbar und hier zu finden:
Click to expand...
Click to collapse
I registered and it still said i'm not allowed to visit the forum because i dont have permission.
D-V-D-K said:
I registered and it still said i'm not allowed to visit the forum because i dont have permission.
Click to expand...
Click to collapse
That's correct, because you did not follow the guidelines.
The activation for this area is done manually by your first post.
Samuelgames said:
If you are an end user I would recommend waiting for WPInternals partition dumps for your device
Click to expand...
Click to collapse
Can you upload your partition dumps for 640xl?
Removed. Sorry I was being rash.
spavlin said:
INF files Qualcomm ARM-based View attachment 4410518
Click to expand...
Click to collapse
but theese inffiles arent redone from registry
for example touch driver is missing
imbushuo said:
- Download a Lumia 2520 recovery image for some files (I will post these files later)
Click to expand...
Click to collapse
Use at your own risk!
Some Lumia 2520 Firmware And Driver Update 10. 6. 2014:
Code:
http://au.ds.download.windowsupdate.com/c/msdownload/update/driver/drvs/2014/03/20623735_d3143757b17f94d00f53dc6f3f4dbdf48c36430e.cab
http://au.ds.download.windowsupdate.com/c/msdownload/update/driver/drvs/2014/03/20624060_4b5dec4829bf5e013bf5e6c045a4ed9367afe88d.cab
http://au.ds.download.windowsupdate.com/c/msdownload/update/driver/drvs/2014/03/20624064_70ea6951b8f7c7d72963c38e302356f46642ec85.cab
http://au.ds.download.windowsupdate.com/c/msdownload/update/driver/drvs/2014/03/20624552_3c10b74a53f010a90539ea1e606f562d65a03082.cab
http://au.ds.download.windowsupdate.com/c/msdownload/update/driver/drvs/2014/03/20626644_7f0f6945d5e0e19e78b3794490990145b98e2c0c.cab
http://au.ds.download.windowsupdate.com/d/msdownload/update/driver/drvs/2014/04/20639225_555ea122b93d34720513db1b344254a0a69a158c.cab
http://au.ds.download.windowsupdate.com/c/msdownload/update/driver/drvs/2014/04/20639552_08956ac77c46334650fc675794d58325f279ddbb.cab
http://au.ds.download.windowsupdate.com/c/msdownload/update/driver/drvs/2014/04/20640693_4d4f789e1349e350324fb7e31b60514ae191cb46.cab
http://au.ds.download.windowsupdate.com/c/msdownload/update/driver/drvs/2014/04/20642401_1278d3d9f4ae8d1903ec0c6f0861ec9912139b96.cab
http://au.ds.download.windowsupdate.com/c/msdownload/update/driver/drvs/2014/04/20643591_beca8afddf93a8679f6e875f5abfc44f9395975a.cab
http://au.ds.download.windowsupdate.com/c/msdownload/update/driver/drvs/2014/04/20643598_4a154479fe2ad83eef04c99e96e44b0e88efce8e.cab
http://au.ds.download.windowsupdate.com/c/msdownload/update/driver/drvs/2014/04/20643814_2d9a86009238af018f92aa76a9be453ef9231424.cab
So Windows 10 on ARM is here, and I have seen a project resulting in Win10 running on an ARM phone (Lumia 950XL)
Does anyone know if there are projects to install Windows 10 on an ARM powered Android Tablet?
Anyone??
Would like to know from someone who undersntad the boot technology on ARM powered Android tabs if its even practical to modify the bootloader to load a windows image.
They can install Win 10 on the Raspberry Pi 3
They can install Win 10 on the Raspberry Pi 3, they should be able to boot in Android and Fire Tables
Afaik, there's no standard UEFI implementation yet that will boot WoA for android devices. You'd also still run into the issue of drivers, we can't just take Android drivers and use them under Windows (different kernels, syscalls and executable format), so porters would need to find or build Windows equivalents.
I also almost forgot, MS is also removing things related to calling and messaging from the system, so viability may not be good anymore.
Some useful links for those reinstalling Windows 10 at any point:
Builds - http://mdluup.ct8.pl
This uses Microsoft's UUP (unified update platform) to fetch specific full builds. Choose from Retail or Insider builds. At the time of writing selecting 17134 from the retail channel will get you the newest non-beta build with minimal Windows Updates following installation. Just specify x64/86/ARM, edition and language.
Using the blue Aria2 button will give you a zip which, on execution, will download and create a usable, full ISO for personal use - despite the use of the words "cumulative update" on-site. Just follow the instructions on screen. All images are compiled using Microsoft's internal imaging utility so they're close to what you'd get with a precompiled MSDN ISO.
MSMG Toolkit - http://m.majorgeeks.com/files/details/msmg_toolkit.html
This provides a frontend for component removal utilizing the official Microsoft DISM utility.
Use of this is straightforward and can remove Apps, Windows Features and components from an ISO.
Tip: Once you've mounted an ISO, open a separate command line and run DISM.exe /Image:<path_to_image_directory> [/Get-ProvisionedAppxPackages to get a full list of Apps in the ISO. Copy and paste the output, placing it in the provided RemoveAppsList.txt, removing any lines you want to keep.
Using install_wim_tweak.exe tool will also get you a full listing of all Windows Packages, most of which can be safely removed with zero side effects. NTLite can be a useful guide but its commercial software, so you won't be able to remove all the components you see listed if you install it.
AIO boot tool - https://www.aioboot.com/en/
This tool creates nifty bootable USB sticks that come in handy for booting anything. I recommend the precompiled WinPE 10 images which allow you to use a Live PE Windows Desktop (I.e. it has a full GUI) from a USB prior to installation. This should alleviate the need for making bootable USBs in future. As it's the same platform used during a conventional booted Windows Setup so you can run the setup once its loaded in, format hard drives, etc. Or actually use it as a desktop, I guess. It has its limitations.
DISM++ - https://www.chuyu.me/en/index.html
Post-install utility, you can thoroughly clean up redundant internal Windows folders, remove Apps, activate popular regedits and whatnot. Very useful.
Blackviper - https://github.com/madbomb122/BlackViperScript
Power shell script that makes running services in Windows slightly more efficient.
If people are interested I'm happy to create a tutorial to making your own properly-serviced Windows ISOs for those who want new builds of Windows with less to none of the Microsoft extras .