Related
For an extremely long amount of time I have tried figuring out why my wifi wasn't working in Windows 8. I finally narrowed it down to the fact that the Wireless card doesn't have the correct drivers. So I go to download the new drivers and when I try to install it won't let me. All it says is I have the wrong version. Even when trying to install in Windows 7 Compatibility mode.
So I simply came to ask, is there a way to force a driver to install?
Or has anyone figured out how to install these drivers?
I have an HP Folio 13 1020us with an Atheros and Broadcom Wifi Cards
Thank you for your time!
normally i would just modify the INF file to include Windows 8 version numbers but the INF is very big and not as clear as id have expected, the bottom two thirds of the INF are meaningless for this task, its the top bit, but i cant see where it does the version check, so either ive missed it or its built in to the executable. if its the latter your screwed unless...
you can try test which its way its doing the version check by extracting the drivers from the exe you download from their website then try manually updating the drivers, by going to device manager, then clicking update drivers on the wireless adaptor, tell it you have the disk and then point it to the INF file you just extracted
i dont have your laptop so i cant test it
dazza9075 said:
normally i would just modify the INF file to include Windows 8 version numbers but the INF is very big and not as clear as id have expected, the bottom two thirds of the INF are meaningless for this task, its the top bit, but i cant see where it does the version check, so either ive missed it or its built in to the executable. if its the latter your screwed unless...
you can try test which its way its doing the version check by extracting the drivers from the exe you download from their website then try manually updating the drivers, by going to device manager, then clicking update drivers on the wireless adaptor, tell it you have the disk and then point it to the INF file you just extracted
i dont have your laptop so i cant test it
Click to expand...
Click to collapse
Oh wow, I just gave almost the same information in his other thread.Tapatalk didn't show this one til after lol
Sent from my LS-LS670 using XDA
I can't install the USB System Drivers for my ViewPad. I'm running Windows 8 RTM and when I try to install the USB drivers, I get this error: The INF-file from Third-Party does not contain any information about digital signature. If you know the name of the device's producer, you can go to the producer's website and look after driver software in the support (The message may not be completly correct, because I needed to translate it from Norwegian) Does anybody have any sugestions?
Unsigned drivers seems to be a major recurring issue with Win 8. There are some workarounds, but none guaranteed to work it seems. Try googling 'unsigned driver install in Windows 8'
This applies to a specific device not on these forums but running Windows 8
I upgraded from Windows 7 on my Viliv N5 and now the webcam and a "Marvell 802.11 sd8686 Wireless LAN SDIO" won't start... I checked both online and computer manufacture... I got drivers from the computer manufacture that hard reboots and one from online with: "Error code:10 Device Cannot Start"
As for the webcam I might have to call the now shutdown business so I'm hoping for a fix...
Did you do an in-place upgrade, or did you do a clean install that replaced Win7? In-place is supposed to work, but in my experience it almost never does it perfectly. Clean install is the way to go. Copy your driver files to a flashdrive or something first in case Win8 can't find them, but usually it can.
Alternate option: Uninstall theoffending drivers (entirely; use Device Manager and remove the driver software). Then reboot the PC and see if it tries to load the drivers from Windows Update. This *should* find them. If it doesn't, try installing the drivers from disc / downloaded files.
Tried Windows Update as soon as I did a CLEAN install... wiped HDD incl recovery >.<
I can provide device id... and the website gives me a corrupt driver
Edit: Will do a "Dirty Install" if I reinstall stock will my key expire?
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
Trying to get these drivers installed on windows 10 machine but no matter which driver i choose it always pops up "windows encountered an error while installing driver". im trying to get into qpst file explorer to see the policy_man folder for the carrier policy. im on havoc rom 11 and there is no engineer mode(*#801, *#800) or log kit since im not factory rom. ive tried disable driver signature verify under advanced restart on the pc....no luck same error. ive tried disable secure boot in bios on pc....same error.
ive tried these steps......
1. adb reboot ftm
2. Install (in your smartphone) USB Gadget Tool (https://f-droid.org/es/packages/net.tjado.usbgadget/) and check this modes: ( cser.dun.O , diag.diag, diag.diag.mdm , ffs.adb , gsi.dpl , gsi.rmnet , qdss.qdss , qdss.qdss.mdm )
3. adb shell su setprop sys.usb.config diag,diag_mdm,adb
4. Disconnect and connect your phone usb cable.
5. Go to Control Panel – Device Manager. You will see some unknown device. You should look at the so-called "Oneplus 8T", ignore the others.
Right click on the first "Oneplus 8T" –> Update Driver –> Browse my computer drivers -> Let me pick form a list of available drivers -> Click on I Have Disk -> Show all devices, browse then go to the Qualcomm Drivers that you download earlier. Then do the same to the other "Oneplus 8T". Choose 9018 for both unknown "Oneplus 8T"..
6. Add both ports in QPST Configuration. Only one of them is the one you are going to use. By clicking on EFS Explorer you will know which one it is by seeing X55 Driver in the description.
7. Change carrier_policy and carrier_policy.xml_Subscription01 files
8. adb reboot
stuck on step 5
Hmmm... You do have the regular drivers for the device installed as well, correct?
(ADB) works? Try this - (Let me know if you need 32 bit installer) No need to disable driver signing enforcement.
10.99 MB file on MEGA
mega.nz
64bit - If it needs a password it's GADGETSDOCTOR
If you're getting into the use of Qualcomm engineering tools check out the fine work of KL Joachim Schepke and the #u100 Crew to make QXDM5g and the accompanying Tools available, search QXDM5 , also includes driver autoinstaller.
Uninstall the old ones and reboot first, go actually delete the directory, Qcomm doesn't uninstall very cleanly.
Let me know how it goes,
-L4X$
L!V3_4_XC3SS said:
Hmmm... You do have the regular drivers for the device installed as well, correct?
(ADB) works? Try this - (Let me know if you need 32 bit installer) No need to disable driver signing enforcement.
10.99 MB file on MEGA
mega.nz
64bit - If it needs a password it's GADGETSDOCTOR
If you're getting into the use of Qualcomm engineering tools check out the fine work of KL Joachim Schepke and the #u100 Crew to make QXDM5g and the accompanying Tools available, search QXDM5 , also includes driver autoinstaller.
Uninstall the old ones and reboot first, go actually delete the directory, Qcomm doesn't uninstall very cleanly.
Let me know how it goes,
-L4X$
Click to expand...
Click to collapse
Hey thx for the reply....if you mean the oneplus drivers, then yes they are installed on pc and adb works(command prompt and all that).
i uninstalled the old ones and rebooted...downloaded that file and installed....trying now
L!V3_4_XC3SS said:
Hmmm... You do have the regular drivers for the device installed as well, correct?
(ADB) works? Try this - (Let me know if you need 32 bit installer) No need to disable driver signing enforcement.
10.99 MB file on MEGA
mega.nz
64bit - If it needs a password it's GADGETSDOCTOR
If you're getting into the use of Qualcomm engineering tools check out the fine work of KL Joachim Schepke and the #u100 Crew to make QXDM5g and the accompanying Tools available, search QXDM5 , also includes driver autoinstaller.
Uninstall the old ones and reboot first, go actually delete the directory, Qcomm doesn't uninstall very cleanly.
Let me know how it goes,
-L4X$
Click to expand...
Click to collapse
I have tried this and no luck, this is preventing me from using msm to convert my 8t and possibly unbrick if needed. No matter how I install these drivers this is what I get after reboot
"Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)"
msi laptop running windows 10 latest update
JayTheKid said:
I have tried this and no luck, this is preventing me from using msm to convert my 8t and possibly unbrick if needed. No matter how I install these drivers this is what I get after reboot
"Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)"
msi laptop running windows 10 latest update
Click to expand...
Click to collapse
i was able to get device manager to show the device(kb2005) and update/install the driver for that....however, it does not show another kb2005 device, just shows 2 'unknown device'. when i try the update/install driver for the 'unknowns', i get the windows has encountered an error message
with only the one driver installed(shows qualcomm android modem 9018 in device manager under modems tab), i still cant get qpst tools to work without both drivers. in qpst, it shows the correct driver installed as active phones and shows under ports tab....and theres no port to add with add new port
fosgate24360 said:
i was able to get device manager to show the device(kb2005) and update/install the driver for that....however, it does not show another kb2005 device, just shows 2 'unknown device'. when i try the update/install driver for the 'unknowns', i get the windows has encountered an error message
with only the one driver installed(shows qualcomm android modem 9018 in device manager under modems tab), i still cant get qpst tools to work without both drivers. in qpst, it shows the correct driver installed as active phones and shows under ports tab....and theres no port to add with add new port
Click to expand...
Click to collapse
Sorry I was traveling for a little bit - did you get this handled? Sounds to me like you need to make sure that your USB & or wireless debugging is active and not just charging, you can change it on your notifications to transfer files or something like that
L!V3_4_XC3SS said:
Sorry I was traveling for a little bit - did you get this handled? Sounds to me like you need to make sure that your USB & or wireless debugging is active and not just charging, you can change it on your notifications to transfer files or something like that
Click to expand...
Click to collapse
no problem....i was able to get it working thank you. i ended up switching over to android12 evolutionx rom. i had to do that same mod with carrier files and the phone does now pick up 5g signal and 5g icon in stat bar
fosgate24360 said:
Trying to get these drivers installed on windows 10 machine but no matter which driver i choose it always pops up "windows encountered an error while installing driver". im trying to get into qpst file explorer to see the policy_man folder for the carrier policy. im on havoc rom 11 and there is no engineer mode(*#801, *#800) or log kit since im not factory rom. ive tried disable driver signature verify under advanced restart on the pc....no luck same error. ive tried disable secure boot in bios on pc....same error.
ive tried these steps......
1. adb reboot ftm
2. Install (in your smartphone) USB Gadget Tool (https://f-droid.org/es/packages/net.tjado.usbgadget/) and check this modes: ( cser.dun.O , diag.diag, diag.diag.mdm , ffs.adb , gsi.dpl , gsi.rmnet , qdss.qdss , qdss.qdss.mdm )
3. adb shell su setprop sys.usb.config diag,diag_mdm,adb
4. Disconnect and connect your phone usb cable.
5. Go to Control Panel – Device Manager. You will see some unknown device. You should look at the so-called "Oneplus 8T", ignore the others.
Right click on the first "Oneplus 8T" –> Update Driver –> Browse my computer drivers -> Let me pick form a list of available drivers -> Click on I Have Disk -> Show all devices, browse then go to the Qualcomm Drivers that you download earlier. Then do the same to the other "Oneplus 8T". Choose 9018 for both unknown "Oneplus 8T"..
6. Add both ports in QPST Configuration. Only one of them is the one you are going to use. By clicking on EFS Explorer you will know which one it is by seeing X55 Driver in the description.
7. Change carrier_policy and carrier_policy.xml_Subscription01 files
8. adb reboot
stuck on step 5
Click to expand...
Click to collapse
What did you do specifically to get this working? I'm having trouble on Step 5 as well and I can't detect a device.
Xryphon said:
What did you do specifically to get this working? I'm having trouble on Step 5 as well and I can't detect a device.
Click to expand...
Click to collapse
Have you tried disabling Driver Signing Enforcement when booting into Windows and then installing the driver?
Xryphon said:
What did you do specifically to get this working? I'm having trouble on Step 5 as well and I can't detect a device.
Click to expand...
Click to collapse
#3 command should start like this:
adb shell
su
setprop....
Also disable Driver Signing Enforcement, as you'll have to install driver every time you want to use QPST, with it enabled.