yashsingh1/xdaforums huggingface dataset:
[Windows 10 Mobile] raghulive:
tutorial updated checkout OP,reply if it worked for u or not
[Windows 10 Mobile] ngame:
Someone please post a fiddler log for this update to so what's changed and caused this boot loop
[Windows 10 Mobile] raghulive:
some people tweeting to gabeaul "updated to redstone through registry edit " don't do that ,they may do even though calls for unsupported devices,like this "Booting loop" :mad:
[Windows 10 Mobile] swiftyste:
my phone didnt even have the BSP release so i added it but with no joy, i made sure everything was right info on my gf phone lumia 435 witch does receive builds. but still nothing anything else worth trying. i give it a bash
[Windows 10 Mobile] kkruglov:
my friend (he has access to non-public builds, for example to .218 1.5 weeks ago, and to this build (14322) a couple of days ago), he has lumia 920 and xiaomi mi4; he told me that only one of the first 143** builds were able to boot on 920, but had reboots every 5-7 minutes, without being used/touched at all. later builds like 14322 doesn't boot at all.
[Windows 10 Mobile] Enderneer:
Does someone know how to get the PhoneManufacturerModelName from lumiafirmware.com?
[Windows 10 Mobile] raghulive:
PhoneManufacturerModelName nothing but
[Windows 10 Mobile] raghulive:
"only 4G or 3G option "in 14322,for those on 10586.xxx request this on feedback app.
[Windows 10 Mobile] BlueTR:
I cant edit keys in ...\Nokia\Variant. What can I do? I have interop, using W10 latest th2 build.
[Windows 10 Mobile] raghulive:
did you able to change other values,restore NDTKsvc in vcreg1.5,reboot and try again
[Windows 10 Mobile] Enderneer:
That's the phoneManufacturerName, not the phoneManufacturerModelName.

Never mind, I got it using Google.

---------- Post added at 10:45 AM ---------- Previous post was at 10:41 AM ----------

---------- Post added at 10:46 AM ---------- Previous post was at 10:45 AM ----------

Okay, so using the similar device settings instead of the 950 XL settings (Lumia 1520 settings in my case) also results in the infinite boot loop.

I guess Microsoft just dropped support for the S4 chipsets. Which makes sense, since there are no devices with S4 chipsets in the supported list, as far as I know.

I will just select the Release Preview Ring for now and maybe try again when the next RS build is released.
[Windows 10 Mobile] raghulive:
your 1320 had Qualcomm Snapdragon 400,they just put something to go endless boot loop for unsupported devices while updating.
[Windows 10 Mobile] Enderneer:
Ah, thanks for the info.

So I guess there is still hope?
[Windows 10 Mobile] BlueTR:
I have already done it. Restored again and still cant edit these values. I am able to edit most of the keys in registry except some keys and these are one of them.
[Windows 10 Mobile] ngame:
So you think Lumia 630 users can get this without any problems using registry hack ?
[Windows 10 Mobile] Enderneer:
I don't know.

I probably made a wrong assumption about my phone. It was corrected in this reply:
[Windows 10 Mobile] raghulive:
anyone missing fm radio in 14322,even reset can't get it back for u,fm radio ,heycortana missing ,huge bug,

Radio FM Phone https://www.microsoft.com/store/apps/9wzdncrfhxns ,you will get it back default.

in store,some apps showing pending no status but there in list .in app list they shows ad pending.first turnoff automatic updates option.

first download any new app while downloading click on pause all and after few seconds click on resume all .pending will shows completed.
[Windows 10 Mobile] T0BlAS:
According to Microsoft, the 1320 has also a S4:

link
[Windows 10 Mobile] raghulive:
Yes you are right ,gsmarena mentioned sd 400,
[Windows 10 Mobile] dape16:
Anyone tried on a Lumia 1020 yet? I guess it will be bootloop just as 920. I use my 1020 as a backup phone right now so I can't try.

I think it is just ridiculous that the 1020 with 2 GB RAM that runs 10586.218 just fine (performance wise, only some general W10 bugs), will not be able to continue the Windows Insider program and receive Redstone builds.

I actually bought my Lumia 1020 (quite expensive) after Microsofts promise that it would receive Windows 10. Now it won't get any official update and the 10586 builds will be the last insider builds it will get. The 10586 Threshold builds will soon be obsolete when Redstone goes RTM with "messaging everywhere" and other features, even some new apps will apparently require Redstone API's and won't run on 10586.
[Windows 10 Mobile] fer_cabr:
someone already try changing "PhoneSOCVersion" to 8926?

8926 is the snapdragon 400
[Windows 10 Mobile] benneeh:
Sadly the 14322 causes an endless boot loop on the 1020, just tried it.
[Windows 10 Mobile] dape16:
Thanks for reporting!
[Windows 10 Mobile] Enderneer:
Hm, I'm tempted to try it, but I've been through two WDRT factory resets since the update. I think I'll wait and see if someone else tries it and if nobody does for a few days, I'll try it again with this tweak.
[Windows 10 Mobile] BlueTR:
Has someone tried to install with new method? Does it still cause boot loop? What happens if we try to upgrade from 8.1?
[Windows 10 Mobile] Enderneer:
It seems like the Lumia 435 is the only eligible device with a dual core processor. So I guess if anything is going to work for a phone with a Snapdragon S4 processor, it might be with the L435 registry entries. I haven't been successful in finding the entries for my country (Germany) yet, but I'll keep looking.

UPDATE: About to try the update one more time (with L435 settings). Will update if successful...
[Windows 10 Mobile] Kenny7:
I have tried to update my Lumia 1020. 14267 was running fine, but with 14322 I only got the boot loop. I had to recover to 8.1 tonight, because this is my main phone... now waiting for suggestion. 10586.107 and the latest redstone were running fine. I dont see any reason not to upgrade
[Windows 10 Mobile] dape16:
Thanks for reporting. I did try to run 14267 on my 1020 but it was really buggy for me, restarting all the time, not usable.
[Windows 10 Mobile] BlueTR:
So, what is the result?
[Windows 10 Mobile] Enderneer:
So far, it's my third boot loop...

Tried the following settings:

HKLM-->SYSTEM-->Platform-->DeviceTargetingInfo

PhoneManufacturer: MicrosoftMDG

PhoneManufacturerModelName: RM-1069_1003

Phonemodelname: Lumia 435

PhoneHardwareVariant: RM-1069

PhoneSOCVersion: 8210

HKLM-->SOFTWARE-->OEM-->Nokia-->Variant

BSPRelease: 2074.0000

ConfigurationID: 1003_0269B6

...To no avail.
[Windows 10 Mobile] swiftyste:
Looking like they have done something to stop us from updating. My phone just doesnt have BSP Release
[Windows 10 Mobile] raghulive:
Did you find corebuildID of 435 and entered it before updating

Sent from mTalk
[Windows 10 Mobile] TristanLeBoss:
If they indeed dropped the Qualcomm S4 cpu, they probably don't provide the cpu driver along with the new redstone builds. Maybe someone can make some use of the cabs from build 15086.218:

3 cabs are need to use QC8960 (Qualcomm S4 used in Lumia 1020, for example) :

CBS version :

http://download.windowsupdate.com/c..._9e1b9c5227bcb60b189a3c51522031e896b93f4c.cab

http://download.windowsupdate.com/c..._3de1701bf2c0f09a01611028be255e45c7eec39b.cab

http://download.windowsupdate.com/c..._d6769d55feeabbdda6975e9c3303c0e2a48289d5.cab

CBS-Update version:

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

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

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

It would be cool if people could contribute to http://xdaforums.com/windows-10/windows-10-mobile/w10m-builds-update-links-collection-cab-t3234805 before they do either a failed or successful update. This way we could understand what has changed.

---------- Post added at 05:52 AM ---------- Previous post was at 05:49 AM ----------

Btw, if someone manage to access the registry of a bootlooped Lumia 1020, it would be interesting to check for these keys:

[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"

They are responsible for QC8960 driver's loading.
[Windows 10 Mobile] BlueTR:
Which registry editor do you use? I just cant edit keys under .../Nokia/Variant
[Windows 10 Mobile] caothuv:
I using Lumia 530 Dual SIM Build 10.0.10586.218 and I can't update builds 14322 with the guidance #1 . Please help me . Tks !
[Windows 10 Mobile] sronweb:
Just follow the posts before your. Your are not the only one with this issue.
[Windows 10 Mobile] swiftyste:
what if your device doesn't have BSPRelease in the list. would it help if i add it or not
[Windows 10 Mobile] sronweb:
At the moment the trick to change the registry to make believe that your phone is a supported one seems to not work. There might be another workaround using different method. I don't know other methods yet, sorry.

As general comment as I see even for the supported device Redstone is not so stable and has several issues which make me think to stay with TH at the moment, especially having a low ram device. But having a spare device where it's possible to play or get unusable for a while it's good to test BRS, otherwise we will never know the progress....
[Windows 10 Mobile] swiftyste:
oh yes i all set up for that. I am trying different methods. just trying the new method but without having the bsp release is stopping me in my tracks. my girl friend is the lucky one with the lumia 435. I am trying any way possible to get on the latest build. it seems stable so far on lumia 435. thats normally on her list is complain but she likes it so far
[Windows 10 Mobile] Enderneer:
No, I wasn't able to find the CorebuildID, but decided to give it a try anyway.

---------- Post added at 10:44 AM ---------- Previous post was at 10:42 AM ----------

I used customPDF this time.

You can try using vcreg 1.5 or root tool http://xdaforums.com/attachment.php?attachmentid=3465583&d=1441629736
[Windows 10 Mobile] BlueTR:
I have all of them but I cant edit some keys. They seem read-only.
[Windows 10 Mobile] devloz:
Do any of you has Lumia 730 Dual SIM CoreBuildID?

I'm on L630DS and changed these values:

"BSPRelease"=2040.0021" (didn't change it since it was the same as mine)

"ConfigurationID"="1021.0265DE"

"PhoneManufacturer"="MicrosoftMDG" // On "NOKIA" I've received update to 14295.1000.

"PhoneHardwareVariant"="RM-1040"

"PhoneManufacturerModelName="RM-1040_1021"

"PhoneModelName"="Lumia 730 Dual SIM"

"PhoneSOCVersion"="8926" (was "8226")

I don't get builds with that change, what should I do?

Important: In the past I was able to get build 14291.1004 without so big modifications (just PhoneManufacturer).

EDIT: Heck. After changing to Slow Ring i've got 14295.1000 :) Maybe after bigger tinkering there'll 143xx?

EDIT2: Unsure if it'll **** me, but I changed CoreBuildID to the one of OP :v

EDIT3: Ugh, forgot to update: my Manufacturer is set to NOKIA (default). Weird it allowed me to download.
[Windows 10 Mobile] Enderneer:
Try following the instructions here carefully:

http://xdaforums.com/showpost.php?p=64410126&postcount=340
[Windows 10 Mobile] BlueTR:
Finally I got permissions to write on ...Nokia\Variant and changed every key (including platformid keys) with Lumia 640 values and I can confirm that this trick doesnt work for Lumia 630 (RM-976) anymore.
[Windows 10 Mobile] Enderneer:
Just posted the cab URLs for my L1320 (updating from 10586.164 to build 10586.218) to the other thread :)

I will try and download Build 14322 one more time via a fiddler proxy just for the sake of comparing the cab files.

Hopefully it won't be too much trouble, I'm getting pretty exhausted But I'll do it in the name of science! :eek:

EDIT: Here are the links to the cab URLs (pastebin).

- Updating from build 10586.164 to build 10586.218: LINK

- Updating from build 10586.218 to build 14322.1000: LINK

It does not seem like they dropped support for the Snapdragon S4 chipset, since the cabs are downloaded for both updates.

(microsoft.soc_qc8960.mainos.cbs_b72729040a1ca6fcd0048315b063ac6efac360bf.cab, for example)

However, the (original) registry entry for PhoneSOCVersion on my device is "8930AB" - which is actually the soc of the Snapdragon 400, not the S4. I wonder if this could have something to do with it? But both updates download the 8960 cabs and the 10586.218 build works like a charm.

Another difference: the 14322 build connected to the following URL: http://statsfe2.update.microsoft.com/ReportingWebService/ReportingWebService.asmx

This is what it says when I put the URL in Internet Explorer:

"Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine."

I am not sure if it was my phone or my laptop though, since fiddler records all connections.

The soc cab files for the respective builds are as follows (downloads in the pastebin URLs)

14322:

- microsoft.devicelayout_qc8960.mainos.cbs_9ea0dc66ba19198badf2a7540b7304182f329082.cab

- microsoft.soc_qc8960.updateos.cbs_bba8f9bacab228c24bea1baf8049dcc6e62df513.cab

- microsoft.soc_qc8960.mainos.cbs_b72729040a1ca6fcd0048315b063ac6efac360bf.cab

10586.218:

- microsoft.soc_qc8960.updateos.cbs_3de1701bf2c0f09a01611028be255e45c7eec39b.cab

- microsoft.soc_qc8960.mainos.cbs_d6769d55feeabbdda6975e9c3303c0e2a48289d5.cab

EDIT 2:

If anybody else would like to submit their cab URLS, you can download the update using fiddler (you can configure fiddler as a proxy (Tutorial for iOS - can be applied to W10m) and capture the downloads.

If you restart your phone once the downloading is complete (before it starts installing), you can reset your phone without having to install the update and getting into the bootloop This worked for me. I cannot guarantee it will work for everyone.
[Windows 10 Mobile] devloz:
L630DS user:

Heck. After changing to Slow Ring i've got 14295.1000 :) Maybe after bigger tinkering there'll 143xx?

(but Fast Ring didn't get anything - maybe ring refresh is necessary?)

http://xdaforums.com/showpost.php?p=66390671&postcount=306
[Windows 10 Mobile] ven07:
Just adding.. Changed my modelname to Lumia 950 and only that also allowed me to download 143xx.

Was wondering if I should change it to 930 and try again, but after resetting 3 times by now, I'm kind of tired lol
[Windows 10 Mobile] BlueTR:
So did you get the latest update? If you could, I will try to change my values with 730 single sim and try on my 630 single sim.

Edit: I changed keys in variant and devicetargeting and selected slow ring on insider. Now, I am downloading 10.0.14295.1000. I will keep trying untill I got 143xx.
[Windows 10 Mobile] devloz:
Still at 14295.1000. I'll try more tomorrow.
[Windows 10 Mobile] BlueTR:
I let my phone to do everything. When I woke up I saw 14295 was installed but 143xx wasnt here. I checked updates, enrolled fast ring but no luck. Changed keys with 950 but still cant get it.
[Windows 10 Mobile] devloz:
The same. I've tried to be L535DS, L730DS, and L640DS with no luck.

EDIT: I mean, I've tried to pretend to be these models. Device is 630DS.
[Windows 10 Mobile] raghulive:
730Ds in supported list,no need to regedit
[Windows 10 Mobile] raghulive:
I don't have any other device, other than 1520,for those who want to play can change below values too and try again

Sent from mTalk
[Windows 10 Mobile] BlueTR:
What happens if we change PhoneFirmwareVersion?
[Windows 10 Mobile] raghulive:
you can change it,if you change it ,it will not avoid bugs like booting loop.we change it to get update only,they make something structure /configuration to go boot loop if they don't match with supported list devices config.

if you change FW,you need to change other places also ,like lable id(corebuild id),other device firmware version had update then it will automatically download as insider and failed at end due to difference in HW.
[Windows 10 Mobile] djtonka:
you can't install RS on unsupported devices. Reason for that is simple, there is no packages for older SOC any more. It will break your device every time when you try download and install by cheating OTA server.
[Windows 10 Mobile] Enderneer:
The cab files for the S4 chipset still get downloaded.

Here are the cab files that got downloaded when I updated my Lumia1320 to build 14322:

http://pastebin.com/qhW6Uqsn

So I think it's got to be something else.
[Windows 10 Mobile] djtonka:
those are only Lang CAB's packages. Nothing more
[Windows 10 Mobile] Enderneer:
If you open the file:

microsoft.soc_qc8960.mainos.cbs_b72729040a1ca6fcd0048315b063ac6efac360bf.cab

It contains the folder tree:

windows-->System32-->drivers-->SOCprodTest.sys

Doesn't look like a language package to me.
[Windows 10 Mobile] devloz:
But Snapdragon 400 devices are still supported except for some unlucky 512MB models. Do any of you found cloaking method for Snap-400?

PS: Still on 14295.100 :/
[Windows 10 Mobile] Enderneer:
I just compared the CABs containing the drivers for the respective builds.

The CAB files in Build 10586 contain the driver SOCProdTest.sys as well as the three DLL files (HalExtQ...) and a REG file called "Microsoft.SOC_QC8960.UpdateOS.reg"

The reg file contains the three keys you mentioned.

The CAB files that downloaded with Build 14322 contain the same driver and the 3 DLL files. However, there is no REG file.

Maybe it's worth trying to add the reg file to the 14322 cab file where it's missing and deploying the update with iutool - or just replacing the two chipset CABs from build 14322 with the ones from build 10586?

I won't be able to try it today, since I have to work tomorrow and need my phone in a working condition...
[Windows 10 Mobile] TristanLeBoss:
From Enderneer research (http://xdaforums.com/showpost.php?p=66398549&postcount=309), it seems that the SOC packages are still delivered and are still compiled by MS. But they lack a registry file to register the drivers (http://xdaforums.com/showpost.php?p=66416211&postcount=325) ! The bootloop maybe comes from here...
[Windows 10 Mobile] TristanLeBoss:
I don't think it's worth it to modify a cab file... indeed, there is a `update.cat` file which contains the digital signature of each files contained inside the cab. Modifying one of them will render its digital signature invalid. I doubt that the cab will then be able to be installed but who knows?

I compared the cab from the 2 versions and, if you ignore the version numbers and the hashes here and there, all the files are the same except the missing `reg` file, the missing `file` tag for the reg file in one of the (xml) `manifest` file. The drivers files, once their digital signatures are removed, reveal they are binary same except the file `SOCProdTest.sys` which is different: maybe this is the (real) culprit?

The drivers files are all `Copyright (C) Qualcomm Technologies, Inc. All rights reserved.` except the `SOCProdTest.sys`... which is mostly zero-filled (2480 non-zeo bytes out of 32768).

The main problem comes from the fact that the phone is bootlooping which implies nothing can be tried on it... checking for the registry entries, replacing the SOCProdTest.sys file from 218, reinstalling the cab from 218 would be a cool tries.
[Windows 10 Mobile] titi66200:
Cab microsoft.soc_qc8960.mainos.cbs_b72729040a1ca6fcd0048315b063ac6efac360bf.cab"

in "arm_microsoft.soc_qc8960.mainos1_628844477771337a_8.15.14322.1000_none_c42f69a79b837993.manifest" you have the keys

</registryKey>
<registryKey keyName="HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\OsExtensionDatabase">
<securityDescriptor name="SD0" />
</registryKey>
<registryKey keyName="HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\OsExtensionDatabase\VEN_QCOM&DEV_1001">
<registryValue name="HalExtension" value="HalExtQ8660Timers.dll" valueType="REG_SZ" mutable="true" />
<securityDescriptor name="SD0" />
</registryKey>
<registryKey keyName="HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\OsExtensionDatabase\VEN_QCOM&DEV_1002">
<registryValue name="HalExtension" value="HalExtQcAdm3Dma.dll" valueType="REG_SZ" mutable="true" />
<securityDescriptor name="SD0" />
</registryKey>
<registryKey keyName="HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\OsExtensionDatabase\VEN_QCOM&DEV_1005">
<registryValue name="HalExtension" value="HalExtQ8x60Bam.dll" valueType="REG_SZ" mutable="true" />
<securityDescriptor name="SD0" />
</registryKey>
[Windows 10 Mobile] Enderneer:
The minimum hardware requirements for Windows 10 mobile version 1607 (Redstone/Anniversary Update) are detailed here:

https://msdn.microsoft.com/en-us/li...2459594)(TnL5HPStwNw-aXvS5x0ZwwsvRaeA0ysXeg)()

The supported SOCs are listed in table 6:

Table 6: SoCs supported in Windows Phones that can be updated to Windows 10 Mobile

Manufacturer

Qualcomm Technologies, Inc.

SoC

MSM8x10, MSM8x12, MSM8x26, MSM8916, MSM8926, MSM8x28, MSM8928, MSM8974, MSM8974Pro, MSM8960, MSM8260A, MSM8660A, MSM8930AA, MSM8930AB, MSM8630, MSM8230, MSM8627, MSM8227, MSM8994, MSM8992, MSM8952, MSM8909, MSM8208

So it doesn't look like they're dropping support for the S4 chipset. Who knows, maybe a later build will not result in a boot loop.

---------- Post added at 12:44 PM ---------- Previous post was at 12:37 PM ----------

I think I will take another look at the files and give it a try with the replaced SOCProdTest.sys file either tonight, tomorrow or the day after (since I have Thursday off). I want to revert back to 8.1 anyway so that I can collect the cabs from the 8.1-->10 update before MS blocks access to the Windows Insider app. So I don't have much to lose.

Do you know how to push cabs using iutools? I find the post that describes it a little unclear.
[Windows 10 Mobile] devloz:
Core Build ID would be appreciated :)

EDIT: Can we download cabs and enforce their installation somehow? Just for the sake of science :p
[Windows 10 Mobile] MattyG53602:
HELP!

Hello all the time when im deploying pdf it show error 0x81030120 anyone can help? thx a lot
[Windows 10 Mobile] titi66200:
Your phone is INTEROP Unlock?
[Windows 10 Mobile] O-Dawg:
I updated my Icon to 14295, thanks for the awesome guide. Is it safe to re-enable automatic app updates?

Should I try to continue on to 14322 or will it unquestionably result in boot loop? Phone has Snapdragon 800 processor.

EDIT: I checked the chip SoC version and it is in the supported list (8974, table 6)
[Windows 10 Mobile] Enderneer:
I'm not sure, but I think it is only dual core devices that are getting the bootloop. The Snapdragon 800 is a quad core processor, so I think it should work. But don't take my word for it.

It's safe to re-enable automatic app updates.

Sent from mTalk

---------- Post added at 04:50 PM ---------- Previous post was at 04:38 PM ----------

There is a guide for getting the cabs here: http://xdaforums.com/windows-10/windows-10-mobile/w10m-builds-update-links-collection-cab-t3234805

If you can't find cabs for your device in the post, you will have to use fiddler to get the download URLs.

Just open fiddler and set up your Wi-Fi as a proxy on your phone with your computer's IP (the one running fiddler) and port 8888. You have to enable remote connections in the fiddler settings.

You can test if you set everything up correctly by going to google on your phone. The links should show up in fiddler.

Then enter fast ring and update. Fiddler will capture the download URLs. If your phone can't find updates, disable the proxy again and re-enable it as soon as your phone finds the updates (or you won't be able to capture the URLs).

When the updates for build 14322 have finished downloading, you can restart and hard reset your phone to prevent the update from installing and getting into a bootloop.

I haven't tried pushing any cabs yet myself, so I can't help you on that. Will probably look into it on Wednesday or Thursday.

Sent from mTalk