yashsingh1/xdaforums huggingface dataset:
[Windows 10 Mobile] dape16:
I have now tried this on the 14332 build. The phone is not bootlooping anymore, now it is stuck at the Nokia logo, so there is no visible error code unfortunatly.

I can't find the "winevt" folder anywhere.

I have opened crash dump files found in Data\SystemData\Telemetry\KernelDumps and there is an error code (0x000000b4) saying VIDEO_DRIVER_INIT_FAILURE

In the watchdog crash dump files in the LiveDumps folder there is an error code, 0x00000193 (= ERROR_PROCESS_MODE_NOT_BACKGROUND according to MSDN).
[Windows 10 Mobile] TristanLeBoss:
Thanks. I help but I don't have a Windows phone myself ;)

At least, we are making some progress here: the bootloop is now for sure due to a crash. It's probably the first one "VIDEO_DRIVER_INIT_FAILURE" as if Windows can't init the graphic card, it will probably not continue. (They really did all they can to hide the blue screen ;) )

In a phone, the graphic card is part of the SoC (the Qualcomm chip like the MSM8960 for the Lumia 1020 which comes with the "Adreno 225" graphic processor [gpu]). I am wondering where is the graphic driver!?

If I take a look at the cabs file installed when a phone is upgraded from 8.10 to 10 (stable), there is no cab from Qualcomm. Same thing if you upgrade 10 (stable) to 10 (preview). So Windows 10 probably reuses the Qualcomm cabs from 8.10: I highly think the (8.10 -> 10) upgrade doesn't format the phone, it just updates Windows 8.1 to 10.

Regarding the event log, maybe this is not available on the phone. You may want to check if the registry key "HKLM\SYSTEM\CurrentControlSet\services\eventlog" exists: if it does, look for subfolders like "Application", "Security", "System", they may contains a "File" value with the location of the log file.

The OneCore idea of Microsoft is a genius one: the phone behaves like a computer and vice-versa!

---------- Post added at 12:47 AM ---------- Previous post was at 12:23 AM ----------

Ok, I think the graphic driver is a file named "qcdxkmXXXX.sys" for "Qualcomm Universal DirectX Kernel-Mode Driver". The package is: "Qualcomm.QCXXXX.qcdxdriver.spkg" (XXXX refers to the numbers in the SoC name [MSMXXXX] of your phone). The file should be in "\SystemRoot\System32\drivers". If the driver is installed, there should be a "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\QCDX" registry key to load it.

---------- Post added at 01:10 AM ---------- Previous post was at 12:47 AM ----------

Ok, there is actually 2 packages linked to graphics: the one I talked about previously and another one. The new one is "qcdx11compilerXXXX.dll" for "Qualcomm Adreno Graphics Shader Compiler".

I am now thinking that maybe:

1) there is an incompatibility with the driver and the new Windows versions,

2) the drivers are missing,

3) they are not anymore properly configured in the registry.

It may be worth checking the usual registry keys for the graphic subsystem:

HKEY_LOCAL_MACHINE\hardware\DeviceMap\Video

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\QCDX
[Windows 10 Mobile] dape16:
[MENTION=269273]TristanLeBoss[/MENTION]

Thanks for the info :)

It's strange that MS says that the MSM8960 is supported in W10 version 1607 (Redstone RTM) but on the same time no Lumias with that SoC will get the W10 update.
[Windows 10 Mobile] akhilkalwakurthy:
Is it possible to access the lumia registry values when the phone is boot looping/stuck on nokia logo?

Is it possible to boot phone into mass storage mode when it is boot looping/stuck on nokia logo?
[Windows 10 Mobile] dape16:
Yes to both questions. Altough the HARDWARE registry hive is created on the fly when booting and I havn't found a way to access it, but the other hives are located in files so they can be read/edited.
[Windows 10 Mobile] akhilkalwakurthy:
can you please tell me how to edit registry keys for lumia stuck on nokia logo? I want to see the diiferences between registry values of builds 10586.318 and 14332
[Windows 10 Mobile] dape16:
Of course. :)

Use WPInternals to unlock bootloader and enter mass storage mode.

Then you find the registry files in the folder MainOS\Windows\System32\config

Open regedit and select a root key in your computer registry, press "Load Hive" and select one of the files in folder above, give it a name like W10M and it will be loaded under your root key.

When finished you press "Unload Hive" and any changes will be written to the file! So I highly recommend to make a backup of the original registry files first.
[Windows 10 Mobile] akhilkalwakurthy:
thank you dape16, i'm trying it now. i'll post the differences as soon as I find them.
[Windows 10 Mobile] dape16:
I have found this:

It seems like EventLog not are used in W10M.

The .sys graphics driver is present in 14332 too, but I couldn't find the dll file in 14332 or 10586.

I couldn't access the HARDWARE hive in the registry since it is not located in any file, but the SYSTEM hive is accessible. The Control\Video and Services\QCDX keys are identical to 10586 and points to the .sys graphics driver.

The Control\GraphicsDriver was missing some Configuration keys with sub keys compared to 10586 (it could be keys that are created during the first successful boot). I tried to copy the GraphicsDriver keys from 10586, but it made no difference.

If MS information is correct, that the MSM8960 SoC is supported in the Redstone RTM build I guess there is a small chance that later Redstone builds actually will work on these devices.
[Windows 10 Mobile] akhilkalwakurthy:
same here, couldn't find much difference in SYSTEM registry keys, can't access HARDWARE keys
[Windows 10 Mobile] TristanLeBoss:
Below is the list of the supported phones for Windows 10 Mobile Insider Preview along with their CPU and GPU.

We end up with:

CPUs: Qualcomm Snapdragon MSM8210, MSM8212, MSM8226, MSM8909, MSM8909 v2, MSM8916, MSM8926, MSM8974, MSM8974AA, MSM8974AC, MSM8992, MSM8994

GPUs: Qualcomm Adreno 302, 304, 305, 306, 330, 418, 430

Full list:

Qualcomm MSM8210 Snapdragon 200 / Qualcomm Adreno 302

- Lumia 430

- Lumia 435

Qualcomm MSM8212 Snapdragon 200 / Qualcomm Adreno 302

- Lumia 532

- Lumia 535

- Lumia 540

- BLU Win HD W510U

Qualcomm MSM8226 Snapdragon 400 / Qualcomm Adreno 305

- Lumia 640 XL

Qualcomm MSM8909 Snapdragon 210 / Qualcomm Adreno 304

- Alcatel OneTouch Fierce XL

- Lumia 550

Qualcomm MSM8909 v2 Snapdragon 212 / Qualcomm Adreno 304

- Lumia 650

Qualcomm MSM8916 Snapdragon 410 / Qualcomm Adreno 306

- Mouse Computer Madosma Q501

- BLU Win JR x130e

- BLU Win HD LTE X150Q

- BLU Win HD LTE x150e

Qualcomm MSM8926 Snapdragon 400 / Qualcomm Adreno 305

- Lumia 635

- Lumia 636

- Lumia 638

- Lumia 640

- Lumia 730

- Lumia 735

- Lumia 830

Qualcomm MSM8974 Snapdragon 800 / Qualcomm Adreno 330

- Lumia 929 (Icon)

- Lumia 1520

Qualcomm MSM8974AA Snapdragon 800 / Qualcomm Adreno 330

- Lumia 930

Qualcomm MSM8974AC Snapdragon 801 / Qualcomm Adreno 330

- Xiaomi Mi4

Qualcomm MSM8992 Snapdragon 808 / Qualcomm Adreno 418

- Lumia 950

Qualcomm MSM8994 Snapdragon 810 / Qualcomm Adreno 430

- Lumia 950 XL
[Windows 10 Mobile] akhilkalwakurthy:
but, what about MS documentation saying that windows 10 mobile version 1607 will support msm8960?

https://msdn.microsoft.com/en-us/library/windows/hardware/dn915086(v=vs.85).aspx?tduid=(6a3c6fee6aa356ff563ed2daaef235d9)(256380)(2459594)(TnL5HPStwNw-aXvS5x0ZwwsvRaeA0ysXeg)(
[Windows 10 Mobile] TristanLeBoss:
[MENTION=7457474]akhilkalwakurthy[/MENTION] and [MENTION=315511]dape16[/MENTION] : Thank you guys ;)

Ok, so we progressed to find out the problem is with the graphic driver. I forgot to check the bootlog which indeed implies that the file is still present and still loaded but, for some reason, fails.

The only packages related to the SoC (CPU/GPU/...) which are updated druing the migration from Windows 10 (Stable) to 10 (Preview) are "microsoft.soc_qc8960.mainos" and "microsoft.soc_qc8960".

Few weeks ago, [MENTION=6881800]Enderneer[/MENTION] was planning to revert some packages from 10 (Preview) with the one from 10 (Stable): I don't know if he tried these ones.

The latest working packages from 10 (Stable) (the same version is - at least - used with builds 107 and 164) are:

http://download.windowsupdate.com/d..._d9b3f4db23131e83893ad99ce4b4de494f873145.cab

http://download.windowsupdate.com/d..._665446dc603be5317a42bb0e974b73c5943fb644.cab

So the last thing I would try would be to reinstall those packages on a bootlooping phone. They contains the Hardware Abstraction Layer which is a layer of programming that allows a computer operating system to interact with a hardware device at a general or abstract level rather than at a detailed hardware level.

---------- Post added at 02:21 PM ---------- Previous post was at 02:14 PM ----------

It's pure speculation but MSM8960 may still be compatible but it's possible that the drivers which shipped with the already released phones are not compatible anymore. Indeed, those drivers date back from the Windows Phone 8 era and for some of them are really old (up to 5 years). Maybe Microsoft is changing something in the graphic subsystem which is not compatible with the old drivers anymore. They did that in the past... I remember having a ATI All-In-Wonder cards which lost functionnality after the switch to Windows 7.

Qualcomm probably provides updated drivers to manufacturers but Microsoft doesn't want to bother updating them.
[Windows 10 Mobile] akhilkalwakurthy:
Hello [MENTION=269273]TristanLeBoss[/MENTION], I did try to reinstall the cabs related to SoC but, iutool wasn't recognizing my phone. So, I was unable to install those two cabs. Is there any other way to install these cabs?
[Windows 10 Mobile] TristanLeBoss:
I have no idea ;) I just share "global ideas" to solve the problem as I never had a Windows phone :D

I rely on others to give life to my ideas :D

I am sure someone out there can tell you how to do it. [MENTION=6881800]Enderneer[/MENTION] was doing it so it should be possible.

---------- Post added at 02:42 PM ---------- Previous post was at 02:36 PM ----------

Humm, maybe he was doing the other way around: he tried to manually upgrade 10 (Stable) to 10 (Preview). Go back to the posts in this thread whose date is around the 20 of april. Indeed, I isolated ~30 cabs which are mandatory to upgrade 10 (Stable) to 10 (Preview).
[Windows 10 Mobile] TristanLeBoss:
Here is 2 lists of cabs depending on the 10 (Stable) version you have. I think they were posted by Enderneer in the CAB lists post: http://xdaforums.com/windows-10/windows-10-mobile/w10m-builds-update-links-collection-cab-t3234805

Downloading them all (wget -i textfile.txt), removing the 2 SOC_Q8960 cabs and trying to install them all using ioutool. I think you can put all of them in a folder for ioutool to process them all at the same time.

I think Enderneer was trying to push them one by one which can be slow. But, what I wrote at that time may reduce the cab list:
[Windows 10 Mobile] dape16:
It was me that posted these cab lists. :) Cause back then I tried to push cabs from a boot looping redstone build to my phone with a stable 10586 build on it, to try to find which cab or cabs was causing the boot loop. But I just got error messages when my phone was trying to install most cabs so I gave up.

I don't think Iutool can not be used on a boot looping phone, since it uses the OS on the phone to install the cabs.
[Windows 10 Mobile] TristanLeBoss:
Ah ah sorry. Do you remember which errors you got? Maybe the cabs have to be installed in a specific order... Did you try to put all the cabs in the same folder and ask ioutool to process them or you went to install them one by one?

---------- Post added at 04:21 PM ---------- Previous post was at 04:13 PM ----------

Maybe we can just take the files out of the SOC_Q8960.MainOS cab file I linked and replace them directly on the bootlooping phone drive? Indeed, there is just 4 files:

<DevicePath>\windows\System32\Drivers\SOCProdTest.sys</DevicePath>

<CabPath>3_SOCProd.sys</CabPath>

<DevicePath>\windows\System32\HalExtQ8660Timers.dll</DevicePath>

<CabPath>2_HalExtQ.dll</CabPath>

<DevicePath>\windows\System32\HalExtQ8x60Bam.dll</DevicePath>

<CabPath>5_HalExtQ.dll</CabPath>

<DevicePath>\windows\System32\HalExtQcAdm3Dma.dll</DevicePath>

<CabPath>4_HalExtQ.dll</CabPath>

These files are signed so Windows should not complain.

I don't think the SOC_Q8960.UpdateOS cab is that important.
[Windows 10 Mobile] dape16:
I remember there was some errors about not enough disk space, altough I did a hard reset before trying to push the cabs, so over 20 GB free on data partition. I tried to put all cabs in the folder, and just some cabs (different combinations) and also one by one. The phone did receive them and the errors came after or during the "prepare for update" process.

---------- Post added at 06:40 PM ---------- Previous post was at 06:21 PM ----------

Actually I found out that the SOC_Q8960.UpdateOS cab from a bootlooping redstone build does not include the file Microsoft.SOC_QC8960.UpdateOS.reg, which is included in 10586 builds. This files puts the following entries into the register:

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\OsExtensionDatabase\VEN_QCOM&DEV_1001]

"HalExtension"="HalExtQ8660Timers.dll"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\OsExtensionDatabase\VEN_QCOM&DEV_1002]

"HalExtension"="HalExtQcAdm3Dma.dll"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\OsExtensionDatabase\VEN_QCOM&DEV_1005]

"HalExtension"="HalExtQ8x60Bam.dll"

I just went back to a stable 10586 install on my phone and was planning to wait for newer redstone builds, it takes almost 1,5 - 2 hours to flash and boot a different build so this troubleshooting is a little time consuming ;) But I guess I can multitask when watching ice hockey WC to night. :) Thanks a lot for your ideas!
[Windows 10 Mobile] TristanLeBoss:
Don't worry: I have no more ideas ;) I'm happy we made some improvements in our understanding of what actually happens and how WM10 works. Maybe someone will be able to build up on this.

If you (or someone else!) happen to re-upgrade your phone to a bootlooping version, you can check if these registry keys exists. You can also try to replace the driver files as explained earlier (especially the SOCProdTest.sys which seems to be different). There may be a copy of the file in the Windows\WinSxS folder also; if there is one, try to replace it also.

Enjoy hockey!
[Windows 10 Mobile] titi66200:
Keys are in "arm_microsoft.soc_qc8960.updateos1_xxxxxx.manifest" inside "microsoft.soc_qc8960.updateos.cbs"
[Windows 10 Mobile] TristanLeBoss:
Yes, I saw that too. I am almost sure the keys are also present in the registry (I think we already checked.) The only hope comes from the files which are different between the 10 (Stable) and 10 (Preview).

---------- Post added at 06:40 PM ---------- Previous post was at 06:34 PM ----------

From the "man.dsm.xml" file, the registry file was suposed to be moved to "\windows\Packages\RegistryFiles\Microsoft.SOC_QC8960.UpdateOS.reg".

I don't know what is the "UpdateOS" partition. I just know it's a partition. In Windows 10 IoT, there is a UpdateOS.wim file located in "MainOS:\PROGRAMS\UpdateOS\UpdateOS.wim".
[Windows 10 Mobile] Enderneer:
I don't think they have to be installed in a specific order. I was able to push some cabs one by one and also a bunch in sets back then. While I was trying it, they released a new build, so I tried to get those cabs and restart the process with the new build. But it took longer than I had expected and now I'm too busy with work so I decided to wait until a more stable release comes out (that gets released to the slow ring). Great to see the progress you guys have made since then! I'll definitely try some of your suggestions when I have more time again.
[Windows 10 Mobile] TristanLeBoss:
A new build is available: 10.0.10586.318

Try to grab the cabs URLs using Fiddler.

Someone at windowscentral.com reports that the build works with 1020.

"Using this build from insider preview on 1020 works perfectly. Feels smooth no issues."
[Windows 10 Mobile] TristanLeBoss:
Ok, got the list of all the build 318 cabs: 994 in totals (156 useful cabs, 738 language cabs)! Your phone will only install some of them.

Supported SOCs: QC8909, QC8916, QC8952, QC8960, QC8960_alt_alt, QC8974, QC8994, QC8996, QC8x12, QC8x12_16k, QC8x26, QC8x26_16k

Some mystery: All SOCs have 2 cabs ( microsoft.soc_qcXXXX.mainos.cbs & microsoft.soc_qcXXXX.mainos.cbsu ) except the 8960 which have 2 more related to the UpdateOS partition (microsoft.soc_qc8960.updateos.cbs &microsoft.soc_qc8960.updateos.cbsu).
[Windows 10 Mobile] dape16:
Yes, I updated to 10586.318 yesterday, since it is just a (small) update from 10586.242, (Threshold 2) it was not a big surprise that it was working.

I have installed the bootlooping 14332 on my phone again and have been trying to replace driver files etc. with files from build 14295. I thought it was better to use files from the last booting (but very buggy) redstone build instead of stable 10586. But no success. :(

Sorry if my last post came out wrong, I am honestly thankful for your ideas, maybe it sounded like I was ironic, but I was not. :)
[Windows 10 Mobile] TristanLeBoss:
We had to try! If you did change the SOCProdTest file with the one from the working build and get the same video init error, I'm out of ideas :D AT least, for now, the stable branch still works :D

Don't worry. I got it that way ;) I am not an English native speaker myself...
[Windows 10 Mobile] SalaarZahid:
Hi guys was just wondering maybe the updates are being allowed by Microsoft servers. Maybe it isn't related to missing drivers in newer build or outdated cab files. When the Lumia Icon was again allowed in to the program Gabe said that THEY had changed the judging criteria for the pushing of updates to supported phones. Maybe it's just a back response from the Microsoft servers
[Windows 10 Mobile] djtonka:
yes they did, they changed the status from 2(forbiden) to 4(awaiting) or 1(released) meaning it is allowed by Microsoft servers and available to download but there is no Redstone CAB's packages for specific SOC, not only main vendor MSMxxxx but whole version e.g. MSM8909.P6236.2.0 in case if you trying match more than one device to each other based only on the same MSMxxxx.
[Windows 10 Mobile] akhilkalwakurthy:
hello guys, I tried to check for updates on my lumia 820 running windows 10 build 10586.318 (without changing any registry keys) using fiddler proxy. Update server sent a file "environment.cab" file and my phone said couldn't install updates. When I disconnect fiddler proxy, my phone says "no updates are available". I think this file is a response from windows update server. I may me wrong. I've attached the file. Here is the link to the file https://onedrive.live.com/redir?resid=E724AC567CCD44BE!75463&authkey=!ACBVHxOSC8ZxlWU&ithint=file%2ccab

By the way, can anyone tell me how to boot into mass storage mode when my phone is bootlooping? wp internals is unable to identify my phone. Only windows device recovery tool detects it.
[Windows 10 Mobile] TristanLeBoss:
I checked and it's just a file which tells your phone which Windows Update server to use but thanks for submitting it ;)

The server responsible for the Insider Previews is "wpflights.trafficmanager.net": it tells which version you can download.

For regular builds, the phone uses Windows Update. For Indiser Previews, I don't know if the builds are downloaded from Windows Update or from the WPFlights server.

There used to be a way to fake the answer (http://xdaforums.com/windows-10/windows-10-mobile/howto-install-windows-10-phones-t3030105) from the WPFlights server but Microsoft added a check in the WIndows Insider app to be sure answers come from one of their server (they check the certificate).

If you want, you can install the latest old version which worked with this hack and send us the Fiddler log to see what happens because I think the old version will want to upgrade. If we can bypass the update check and use the old version of the app, the hack may be revived.
[Windows 10 Mobile] TristanLeBoss:
Here is the lastest version without a certificate check.

For the geeks, the certificate check is done in UpdateProvisioning.exe\Microsoft.Phone.Flights.Models\UpdateProvisioningService.cs (decompile the file using ILSpy).

For newer versions, it may be possible to either remove the check ( UpdateProvisioningService.CheckServerCertificate(serverCertificate); ) or to change the certificate SHA1 ( private static readonly byte[][] AcceptedCertThumbprint = new byte[][] ) thanks to ILSpy + Reflexil but there may be problems with the app digital signature: I don't know if you can then install it. Or maybe install it and then patch the file on the drive (replace it).

( It's like the patch that someone made to enable Facebook Messenger under Android: you patch bytes. )
[Windows 10 Mobile] dape16:
Well, there is no problem to install the latest insider builds on unsupported phones with the "old" registry hack.

Or am I misunderstanding what we are trying to achieve here? :)

The device check in the insider app has nothing to do with the latest builds not booting.
[Windows 10 Mobile] TristanLeBoss:
You're right :)

I just post that for the sake of information ;) Also, understanding the way the OS updates may be interesting. With the new version of the app, you can't anymore sniff the HTTPS traffic to the WPFlights server because Fiddler inserts a man in the middle and so change the SSL certificate the app sees.
[Windows 10 Mobile] dape16:
Thanks, all information is interesting, I didn't know that it is not possible to sniff the traffic any longer.

I wanted to clarify for [MENTION=7138513]SalaarZahid[/MENTION] that the insider app device check is not related to the boot loop. :)
[Windows 10 Mobile] titi66200:
It would be nice to have the "UPDATEOS.wim" before the update and "UPDATEOS.wim" after the bootloop.
[Windows 10 Mobile] TristanLeBoss:
Do you know where is this file and how it's used/what's its purpose?
[Windows 10 Mobile] dape16:
I think that is an image which is triggered and loaded on the reboot during the update process. It has probably it's own kernel and acts like an small OS which is active during the cog wheel screen. I guess that's why it is only used in WP8/WM10 and not on the PC version, where the update process is different.

This way all the files including the Windows kernel can be overwritten/replaced during an update.
[Windows 10 Mobile] titi66200:
It seems that "UPDATEOS.wim" is the same thing as "boot.wim" on a windows DVD.

Windows system loaded into ram.
[Windows 10 Mobile] TristanLeBoss:
Ok, thanks. But how do we know when we are in MainOS or UpdateOS? I mean: when the phone crash with the video init error, are we in MainOS or in UpdateOS?

That's the question because the problem is probably not in MainOS but in UpdateOS instead... :D
[Windows 10 Mobile] dape16:
When the phone starts bootlooping the update process are already finished, it has done a reboot and the cog wheels spin has completed. If it wasn't bootlooping it would just start up the phone.

I also think I noticed somewhere that it is the Windows Loader entry in BCD that's booting, not the UpdateOS which is another entry in BCD.

So my guess would be that it is unlikely a problem with the UpdateOS image. :)

---------- Post added at 01:21 AM ---------- Previous post was at 01:02 AM ----------

I have uploaded them here if you want to take a look:

14295 UpdateOS.wim (booting) http://www70.zippyshare.com/v/lzHzoHMA/file.html

14322 UpdateOS.wim (bootlooping) http://www70.zippyshare.com/v/vdvW3fMY/file.html