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
Related
After making a cooked ROM and before flashing into device, is it possible to run on PC enviroment in some sort of simulation or skin to try it out?
I doubt it.
The stand alone emulator from MS actually runs ARM code and uses a bin image file to load the OS.
Trouble is ROMs for different devices have somewhat different structure and are usually encrypted to some degree.
If a tool does exist to RUN certain ROM on a PC it would have to be leaked from the OEM.
http://www.infoworld.com/d/microsoft-windows/windows-8-arm-chips-it-was-too-good-be-true-173265
Windows 8 can run on ARM processor, if you search windows 8 requierments, it sais 1 ghz procesor, we got 600mhz but maybe it could be enough, minimum ram requierment is 64 mb, so maybe there is a way to port the newly released Windows 8 to Mobile :> Can an dev say if it's possible to run it on X8 or not?
We can't run another OS on our X8
Chris95X8 said:
We can't run another OS on our X8
Click to expand...
Click to collapse
Are u sure?
Yeah it has been confirmed, you can find it in the X8 FAQ too.
Well, maybe they may find a way to do it in the future, who knows...
The Windows 8 will be the most "possible" OS that can be ported into android phone.
It is still unknown now.
edit:
http://forum.xda-developers.com/showthread.php?p=17628173#post17628173
Blagus said:
We have more chances porting Windows 8 ARM version instead of WP7.
Click to expand...
Click to collapse
Yes, we can run another OS on our X8 because now the bootloader is unlocked.
Please do not post ambiguous comments if you are not sure about them.
Chris95X8 said:
Yeah it has been confirmed, you can find it in the X8 FAQ too.
Well, maybe they may find a way to do it in the future, who knows...
Click to expand...
Click to collapse
CM-PRo said:
Yes, we can run another OS on our X8 because now the bootloader is unlocked.
Please do not post ambiguous comments if you are not sure about them.
Click to expand...
Click to collapse
Not only the bootloader.
We need the driver and hardware support too.
Yes is only for theory, still many things to do beside of these.
it will be great if we port Windows 8 to our phone but...
It's a really HARD WORK because we need to write all the drivers and probably it will not be as smooth as android because of our processor i think.
But we can run W8 on our device, but we will spend the same time porting it to our phone, as Microsoft creating the next Windows OS
Sorry for my bad english
btw,because win8 is big, it will have to run from sdcard, and also if the card is at least class 6, windows will run pretty fast on our device.. lets keep our ringers crossed
Sent from my X8 using XDA App
i remember there was an easy way of running ubuntu on android device maybe theres an similar solution for running w8...idk just thinking...
Sent from my X8 using XDA App
This is Windows. Not Linux. It means:
We have to take Linux drivers from kernel and rewrite them for Windows
We can't just run it from SD card by Linux-style chrooting. chroot changes root to specified directory, keeping the Linux architecture. That's how you run Ubuntu from SD card and you can't do that with Windows here.
Do we have enough memory? Do you know that loading Windows is different than loading kernel, unpacking which mounts "system", "data" and other partitions? Windows needs only one (1) partition which holds everything.
Of course, you all are invited to take a look at the_laser's boot loader unlock release and try to modify S1Boot calls and functions, to support, for example, booting from SD card as installation media, and merge all partitions into one (maybe exclude amss from that as we could still use radio?) for Windows. Then modify it to execute files from that partition instead of unpacking boot partition and starting Linux boot sequence there.
Do we have enough processing power? Will ARMv6 be supported at all?
And so on...
But still, we have bigger chances in porting Win8 than WP7, assuming that it'll have the standard Windows driver APIs.
Best regards,
Blagus
I think some developers will publish some w8 launchers,lockscreens and themes for theme chooser like we have it today with wp7
Blagus said:
This is Windows. Not Linux. It means:
We have to take Linux drivers from kernel and rewrite them for Windows
We can't just run it from SD card by Linux-style chrooting. chroot changes root to specified directory, keeping the Linux architecture. That's how you run Ubuntu from SD card and you can't do that with Windows here.
Do we have enough memory? Do you know that loading Windows is different than loading kernel, unpacking which mounts "system", "data" and other partitions? Windows needs only one (1) partition which holds everything.
Of course, you all are invited to take a look at the_laser's boot loader unlock release and try to modify S1Boot calls and functions, to support, for example, booting from SD card as installation media, and merge all partitions into one (maybe exclude amss from that as we could still use radio?) for Windows. Then modify it to execute files from that partition instead of unpacking boot partition and starting Linux boot sequence there.
Do we have enough processing power? Will ARMv6 be supported at all?
And so on...
But still, we have bigger chances in porting Win8 than WP7, assuming that it'll have the standard Windows driver APIs.
Best regards,
Blagus
Click to expand...
Click to collapse
Win8 has something like 20GB, if it's similar to Win7, and ARMv6 probably will NOT be supported, we can't have ICS because of the processor, and we are dreaming of having a SO that is, probably, even more heavy in processing.
Keep dreaming of having Win8 on your phones. Install Win8 on your computer to help you having better dreams. And use Teamviewer on X8 to see your Win8 Computer, it will give you a realistic dream.
EDIT: I've changed "W8" to "Win8" because in this foruns the W8 is the Walkman version of our phone, and some people will be confused
Blagus said:
This is Windows. Not Linux. It means:
We have to take Linux drivers from kernel and rewrite them for Windows
We can't just run it from SD card by Linux-style chrooting. chroot changes root to specified directory, keeping the Linux architecture. That's how you run Ubuntu from SD card and you can't do that with Windows here.
Do we have enough memory? Do you know that loading Windows is different than loading kernel, unpacking which mounts "system", "data" and other partitions? Windows needs only one (1) partition which holds everything.
Of course, you all are invited to take a look at the_laser's boot loader unlock release and try to modify S1Boot calls and functions, to support, for example, booting from SD card as installation media, and merge all partitions into one (maybe exclude amss from that as we could still use radio?) for Windows. Then modify it to execute files from that partition instead of unpacking boot partition and starting Linux boot sequence there.
Do we have enough processing power? Will ARMv6 be supported at all?
And so on...
But still, we have bigger chances in porting Win8 than WP7, assuming that it'll have the standard Windows driver APIs.
Best regards,
Blagus
Click to expand...
Click to collapse
well, on system requierments it sais that W8 will even run on an 64 mb ram system, so that's good, but, as you said the processor may be an problem..
Btw, Blagus, thanks for the info now i understand how much work is to do
Does it means Windows Mobile 8 or Windows 8 (computer??)
the requirements already said that we just need 60 mb ram to run win8, does we need the bigger of that? ( i mean does we need more internal memory??)
Also we can (maybe) make inter memory to be many parti and link the system to that part, isn't true?? Sorry newbie...
alvian matt said:
Does it means Windows Mobile 8 or Windows 8 (computer??)
the requirements already said that we just need 60 mb ram to run win8, does we need the bigger of that? ( i mean does we need more internal memory??)
Also we can (maybe) make inter memory to be many parti and link the system to that part, isn't true?? Sorry newbie...
Click to expand...
Click to collapse
Well, i was talking about windows 8, it has been released for PC's and Windows tablets, and will be released for ARM tablets too if it hasn't been already.
It needs minimum 64 mb RAM, and it's got around 4-8 gb so we need an big sdcard
Hello,
is it possible to install a full Windows 8 OS on a smartphone with Intel Atom Z2420 or other Intel CPUs?
(No Windows Phone or RT)
huaba91
They have locked bootloaders (almost always) and non ACPI compatible chipsets (sometimes). Can't stick windows on them unfortunately, screen would be too small anyway. Would certainly be cool though.
Bottom line no. The space requirements for a full install of windows is bigger than internal space available on most of the phones out there. An alternative would be to find a way to install a working version on a micro SD.
I think, the installation on a micro sd shouldnt be so hard.
But booting could be the problem.
Or would it be easier to install a "normal" linux version?
huaba91 said:
I think, the installation on a micro sd shouldnt be so hard.
But booting could be the problem.
Or would it be easier to install a "normal" linux version?
Click to expand...
Click to collapse
The CPU's in most phones can only boot from the onboard flash as is. The hardware doesnt support more.
Clovertrail *by design* can only load windows *or* android (it was sold in 2 versions to do so). The windows version physically cannot load anything else, the android version cannot load anything else.
Eliminates microSD booting and also booting windows on an intel phone. You may have luck with linux on one but that can be done on ARM handsets already, android itself uses linux so it stands to reason that clovertrail may be fooled into booting it, but I dont see the advantage over an ARM handset in doing so.
I only need the x86 architecture for some programms.
And no android/ubuntu touch
PLain ubuntu has been loaded on android tablets already and they have the same hardware as phones. Most linux software is open source and somewhat easily ported to ARM as is.
Yes, i know.
But i didn´t find something for a x86 phone and if for example full ubuntu on Motorola Razr I or Lenovo K900 is the same ubuntu like on a pc, where i also can run x86-only programms.
So i know the Intel atom in this thing supports Windows 10. I just can't figure out how to get the Windows 10 install disk to boot. Custom boot loader?
AceHack00 said:
So i know the Intel atom in this thing supports Windows 10. I just can't figure out how to get the Windows 10 install disk to boot. Custom boot loader?
Click to expand...
Click to collapse
Custom rom that microsoft has provided.... Win 10 is free for all device's.... Tho you may need a custom recovery in some cases.... Theres also a program that microsoft has that will convert it as long as you have root and able to connect it through usb...
ErocKxMoBz said:
Custom rom that microsoft has provided.... Win 10 is free for all device's.... Tho you may need a custom recovery in some cases.... Theres also a program that microsoft has that will convert it as long as you have root and able to connect it through usb...
Click to expand...
Click to collapse
This is... Just wrong. Microsoft provides no special tool to convert android devices into windows 10. They have released Windows 10 Mobile ROMs for 2 devices and they aren't distributed in a way that they can be ported.
Nt true i have a few tablets with intel inside that ran on android i just ran the roms with a bootloader and yea as for the program its not by microsoft exacly but a company they own.. And another thing look at china they have tens of thousands of differnt devices that run both virtualy. Using a custom bootloader
ErocKxMoBz said:
Nt true i have a few tablets with intel inside that ran on android i just ran the roms with a bootloader and yea as for the program its not by microsoft exacly but a company they own.. And another thing look at china they have tens of thousands of differnt devices that run both virtualy. Using a custom bootloader
Click to expand...
Click to collapse
Got any links or how to?
AceHack00 said:
Got any links or how to?
Click to expand...
Click to collapse
No. And there won't be.
ErocKxMoBz said:
Nt true i have a few tablets with intel inside that ran on android i just ran the roms with a bootloader and yea as for the program its not by microsoft exacly but a company they own.. And another thing look at china they have tens of thousands of differnt devices that run both virtualy. Using a custom bootloader
Click to expand...
Click to collapse
Ok, those Intel tablets you refer to probably use a legacy bios booting system, which would support both Android in the x86 variant, and Windows x86. And MAYBE they support a custom bootloader, but I doubt it (you could provide some links as proof). If you refer to the Windows 10 Mobile ROM released for the Chinese phone a while back. That is literally the one exception, but it isn't Windows 10. Its Windows 10 Mobile, which isn't nearly as full featured, and provides no admin level access. And before someone mentions it, NO this cannot be ported to other devices, Android is much easier to port due to the fact that we know how things function due to the Open Source nature of Android, but Windows is not, and likely never will be Open Source.
Now, onto the "custom bootloader" you refer to. Firstly, no Nexus device EVER has been able to run a custom bootloader (lest I mention the Nexus One with S-OFF). All Nexus devices EVER (yes, even after unlocking the bootloader) enforce aboot (high level bootloader) signature verification, they just don't enforce kernel/recovery partition signature checks when the bootloader is unlocked. This means that flashing an unsigned bootloader (no, you can't sign a bootloader yourself, it would have to be released by Google, which they have NEVER done).
You also mentioned running it virtually? Did you mean like Hardware virtualization like VirtualBox and VMware? Good luck finding a functional x86 Virtual Machine manager for Android that doesn't run horribly.
And without links, or any proof, I have never heard of Microsoft (or any subsidiary) releasing a tool to convert Android phones into Windows phones. Because, it just isn't that simple. You don't just install a program and boom, its Windows 10. It requires a complete re-flash of the device, and different bootloader (which I told you is impossible on this device above), it would also require drivers that are more than likely closed source, or don't exist for the Windows platform.
Don't just go saying things you /think/ are possible. Just cause a CPU architecture matches the requirement of the OS doesn't mean that that. OS will ever run. Much more is required.
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