yashsingh1/xdaforums huggingface dataset:
[Windows 10 Mobile] Enderneer:
Here are some of the checks they do when checking for updates (build 14322):

Key="HKEY_LOCAL_MACHINE" Subkey="Software\Microsoft\Windows\CurrentVersion\DeviceUpdate\Agent\Protocol" Value="TestTarget" Comparison="EqualTo" Data="3d73e726-9ce9-4207-832e-2b973e5a10d5"

/><CspQuery Comparison="GreaterThan" LocUri="./DevDetail/Ext/Microsoft/TotalRAM"

/><Or><b.RegSz Key="HKEY_LOCAL_MACHINE" Subkey="System\Platform\DeviceTargetingInfo" Value="PhoneModelName" Comparison="EqualTo" Data="LUMIA 1520"

/><b.RegSz Key="HKEY_LOCAL_MACHINE" Subkey="System\Platform\DeviceTargetingInfo" Value="PhoneModelName" Comparison="EqualTo" Data="RM-937

/><b.RegSz Key="HKEY_LOCAL_MACHINE" Subkey="System\Platform\DeviceTargetingInfo" Value="PhoneModelName" Comparison="EqualTo" Data="RM-938"

/><b.RegSz Key="HKEY_LOCAL_MACHINE" Subkey="System\Platform\DeviceTargetingInfo" Value="PhoneModelName" Comparison="EqualTo" Data="Lumia 430 Dual SIM"

So they don't even seem to check for the manufacturer anymore. Are you connected to a proxy/VPN or something? It will always say your phone is up to date if it's connected to a proxy. Or start up Windows Insider again, select your ring and check again.
[Windows 10 Mobile] AntiBillOS:
Try. But it don't work :(
[Windows 10 Mobile] raghulive:
14328 had some goodies like direct wifi screen share to PC,improved notification with hero images,Messaging everywhere & had some other unnoticeable changes.

in battery usage usually we see "display" had higher % of usage ,but now it shows now as start had using higher % as it refreshes for live tiles :good: & battery life improved with day to day usage, these all changes are going in cool way to make WM 10 is better than 8.1 in near future build or anniversary build in july:)
[Windows 10 Mobile] AntiBillOS:
Thank you. Something of this help me.
[Windows 10 Mobile] ven07:
So you changed RAM/PhoneModelName and RM#?
[Windows 10 Mobile] ADeltaX:
Does someone tried to install redstone on 630/635? It go into bootloop state?

I'd like to find a solution.....
[Windows 10 Mobile] s0rata:
Install on Lumia 920, no bootloop (Slow Ring)

Using the above method, I can install the build on the slow ring (14295) without bootloop issue.

Something to mention, before I restarted my phone, I change all the registry values back to the original.

No issues found, since slow ring has less bugs. So I am gonna stick to this slow ring and get later build in slow ring.
[Windows 10 Mobile] ven07:
We can only go as far as 14295 with unsupported phones. The other two builds cause bootloops :)

Most of us were on 14295
[Windows 10 Mobile] s0rata:
Oh, i didn't know that. so the next build on the slow ring will be the problem. :(

Well, there will be solution for this. I hope.
[Windows 10 Mobile] ven07:
Yea the 143xx builds have caused all to go into bootloops. So far no solutions.

However it might just be sth with the 143xx builds :) from files posted by another user, it seems that the SoC of the 920 is still mentioned.

Think I'll wait for a Release Ring build before attempting anything again. Quite annoying to have to downgrade all the way to 8.x and come back to 10
[Windows 10 Mobile] ADeltaX:
I'm updating all drivers and firmware of my lumia 920 before I upgrade to "Insider Fast Ring" Redstone.

With that I'll know the problem.
[Windows 10 Mobile] ven07:
Keep us in the loop :D (pun intended)
[Windows 10 Mobile] lolasher:
That means that on 512 MB RAM devices I can't even try to get bootloop?
[Windows 10 Mobile] aaryndo:
Registry entries for 920

Hello,

For Lumia 920, which hardware version did you use, the one for Lumia 950XL? or another one?

What steps do you take after registry change? When I open 'Informations' in settings, I see that my phone is Lumia 950XL, than I select Slow or Fast ring in the Insider app, the phone reboots, and than when I check for updates manually, the tool shows me, that the software is up to date. Do I miss something?

In the registry I changed the following entries:

PhoneManufacturerModelName

PhoneManufacturer

PhoneModelName

ConfigurationID
[Windows 10 Mobile] Enderneer:
I'm not sure how much RAM they check for or if they actually check for how much memory the device has as a criteria for whether it gets the update or not. As far as I know, a CSP query usually checks with an online data base according to variable criteria. So it could also be checking which cab files to push depending on the available RAM.

It is possible that you are out of luck (or in luck if you don't want a bootloop :p). But you can always try.

---------- Post added at 08:28 PM ---------- Previous post was at 08:26 PM ----------

Did you change it to "Lumia 950XL" or to "Lumia 950 XL"?

The space between the number and the "XL" is important.
[Windows 10 Mobile] ADeltaX:
Working on updating drivers (from L950, they are very similar to L920, no jk) and editing registry-hives.

Is going very well, and now is faster than before (Just Microsoft doesn't want to update x2x series to W10M for marketing....).
[Windows 10 Mobile] ven07:
Just goes to show that they simply didn't want to do it... I understand them, but I don't at the same time...
[Windows 10 Mobile] raghulive:
the boot loop started at >14295 ,14322,14328 had new features ,for these there may be some new registry changes which are applied perfectly for supported devices while migrating,unsupported devices failed to apply those resulting in boot loop,so next slow ring also causes same boot loop

Sent from mTalk
[Windows 10 Mobile] lolasher:
I tried, entered all possible values from 535 (same SOC in my 530) and there is only 14295 in slow and nothing in fast.
[Windows 10 Mobile] aaryndo:
Thanks very much for your help. The phone name was OK (Lumia 950 XL). I asked the question, because my phone couldn't find the update in the morning, just after changing the registry entries. But when I started my phone in the evening, the update was found. Now a fresh update to 14295 waits for me :)
[Windows 10 Mobile] raghulive:
anybody tried 14332.1001(just 150Mb download size from 14328),still had boot-loop?
[Windows 10 Mobile] spavlin:
ATIV-S Update From 10586.218 to 14332.1001 - boot-loop

View attachment ImgUpd.log
[Windows 10 Mobile] yogesharya2011:
I have lumia 520,8gb internal ,512ram india nd want to try redstone,plz tell me procedure bcz above all procedure not help me to get update so tell me specofic procedure which definitly give me redstone update ,reply me on this email id (yogesh.arya2011@gmail.com) reply fast sir waiting of using redstone in my lumia

---------- Post added at 04:17 AM ---------- Previous post was at 04:02 AM ----------

My lumia 520 win10m build 586.218,plz tell me how can i upgrade to redstone bcz above prescribe tool not working for me,i have tried a lot using different hansed registry but no update found in my lumia 520,i know u are genious so tell me specific procedure to hack redstone for my lumia 520 india build 586.218, reply soon @ mail id yogesh.arya2011@gmail.com,reply fast sir eagly to use redstone
[Windows 10 Mobile] ven07:
it isn't possible right now and there is no specific procedure so far... get a 640 if you want to test Redstone :)

---------- Post added at 05:31 AM ---------- Previous post was at 05:30 AM ----------

any other news to share so far?
[Windows 10 Mobile] ADeltaX:
Updating to redstone right now, and I'll see if it will go into bootloop or it will works.

EDIT: Bootloop as expected, now i'm investigating...
[Windows 10 Mobile] raghulive:
Even in Supported devices , those who are re-arranging Quick Actions 14328 fall into same Boot-loop(my 1520 ) as it is known issue to reset in change-log,need hardware button Reset.so avoid 14332
[Windows 10 Mobile] lolasher:
You were trying on 520? I can't get my 530 to see any newer update than 14295, I tried registry values from 830, 950 XL and 535 (which has the same SOC).
[Windows 10 Mobile] ADeltaX:
Seems to be winload.efi

Anyway, i'll go back to Windows 10.10586.x and the upgrade to 14295 (the working one from slow-ring).

Then i'll try to capture the file that will be updated when it will upgrade to 14332
[Windows 10 Mobile] ven07:
Mate that's a lot of work.. appreciate it
[Windows 10 Mobile] nbaveja:
For any solution to this issue 50% of windows phone community would be thankful.
[Windows 10 Mobile] ADeltaX:
This is complicated as hell!

Still investigating....

I attach the log of the failed update (extracted from EFIESP partition).

You will see some error like missing files.
[Windows 10 Mobile] TristanLeBoss:
Not sure these are serious errors. Log files tends to be verbose... If a fatal error occurred, I think the whole thing would have failed.

How did you get access to the EFI partition if the phone is bootlooping? Do you have access to the MainOS one (where Windows is actually installed)?

I am wondering how we can debug the boot process of the phone. I think there is a "BCD" file in your EFI partition under ":\EFI\Microsoft\boot".

If you have this file, can you try to edit it with VisualBCD (EasyBCD doesn't work): under "BcdStore" > "{bootmgr}", set "DisplayBootMenu" to "true" and "Timeout" to 30. It will be interesting to see if the phone use the BCD file like a normal Windows 10 installation. After all, if the file is present....
[Windows 10 Mobile] Swordfishx86:
Lumia 925 (RM-892_eu_euro2_324) running 10.0.14295.1000 here. Changed Registry values back to originals after downloading and before restart to install the update.

// but going back to 10.0.10586.218 cause of camera bugs in 14295 :(
[Windows 10 Mobile] ADeltaX:
Yes, I edited BCD file to enable charging when phone is off.

PS: I have access to MainOS, DATA, EFIESP, MMOS, DPP partitions even if my phone is in bootloop.

PS: Later i'll do a photo of the lumia with DisplayBootMenu set to Yes and timeout to 30.
[Windows 10 Mobile] titi66200:
Can you share how enable charging when phone is off.
[Windows 10 Mobile] windgog:
hi.

how did you updates to wp10?

windows insider app do nothing at my 925 =(
[Windows 10 Mobile] Swordfishx86:
Instructions are in the first posts of this thread.
[Windows 10 Mobile] raghulive:
instead of going back ,try to install "Microsoft Camera app" & see if it works Camera app(2016.404.71.0)
[Windows 10 Mobile] s0rata:
When install the camera app, it said the higher version is already install.
[Windows 10 Mobile] Swordfishx86:
Thanks for your suggestion, raghulive, but it came a few hours late. Also I was witnessing an extreme power drain with 14295. Its overall not suitable as a daily driver for me.
[Windows 10 Mobile] ADeltaX:
Here you are:

---------- Post added at 16:49 ---------- Previous post was at 16:47 ----------

When i'll get more time, i'll do a guide!

A "preview":
[Windows 10 Mobile] Swordfishx86:
Nice! Good luck with pressing enter, though ... :p
[Windows 10 Mobile] TristanLeBoss:
and F8....

But, there is an option to use the Metro bootloader so maybe this one is compatible with touch screens:

bcdedit /set {default} bootmenupolicy standard

http://www.askvg.com/how-to-disable...s-vista-and-7-style-boot-loader-in-windows-8/
[Windows 10 Mobile] ADeltaX:
For the id {default} bootmenupolicy is already set to standard.
[Windows 10 Mobile] TristanLeBoss:
It seems to be possible to navigate inside menu with Volume +, Volume - and Camera button for Enter key.

Look at this topic I started: http://xdaforums.com/windows-10/win...-file-windows-mobile-10-t3367614/post66604194

This may help us to find the root cause of the bootloop because we can enable BOOT LOGGING through the boot menu.

So, if you have a bootlooping phone, you may want to try editing the bcd file.

bcdedit /store K:\EFIESP\efi\Microsoft\Boot\BCD /set {default} bootmenupolicy legacy

The selection is made the volume buttons (VOL +, VOL -, Camera - Enter)

bcdedit /store K:\EFIESP\efi\Microsoft\Boot\BCD /set {bootloadersettings} advancedoptions Yes

It will then be possible to select "Enable boot logging" which will log all boot actions and maybe, the error which cause the loop.

Maybe we can also trigger the phone to isssue a blue screen instead of looping. I think XP had this option... prevent reboot on error.
[Windows 10 Mobile] ADeltaX:
On lumia, pressing vol up when is in bootmgr, will trigger the Flash mode, while the vol down will trigger the Exclamation mark :\
[Windows 10 Mobile] ven07:
Just a quick side note.. a guide for the hack to set phone to charge while off would be much appreciated and welcomed :)
[Windows 10 Mobile] w.bogdan:
+1 Charging a Lumia phone while switched off would be great

But this conversation should really be kept on the dedicated topic Can we edit BCD file of Windows Mobile 10 ?. It would be easier to follow the progress and exchange ideas then on a general thread.
[Windows 10 Mobile] winphouser:
[MENTION=7415473]ven07[/MENTION] [MENTION=6216929]w.bogdan[/MENTION] For power off charging, try the toggle in original WPTweaker.
[Windows 10 Mobile] raghulive:
power off charging working on [MENTION=2159229]sensboston[/MENTION] 'sWPTweaker,but first you need press web update at bottom to get it.:good:

Lumia 1520
[Windows 10 Mobile] augustinionut:
Work on Lumia 640 XL DualSIM with last fast ring insider build.

Work on Lumia 530 with insider build .107.
[Windows 10 Mobile] John Hitch:
This method no longer works.
[Windows 10 Mobile] augustinionut:
Bad post. I was speaking about poweroff charging.
[Windows 10 Mobile] dudeluv:
I had no problems installing vcReg_1.5 and custom pfd 6, but changing everything to the lumia 950 XL and also tried the Lumia 640 LTE would not work.

I have not got it too work on my Nokia Lumia 635 512. Could it be because I only have 512 ram instead of 1gb? Any help appreciated :fingers-crossed:
[Windows 10 Mobile] ngame:
VCReg and CustomPFD doesn't work On L950X: and all other X5X devices . it has a very limited access to some parts of registry .

but it should work on your other phones without any problems if you weren't updated your Extras + Info .

If you did it you have use Restore NDTKSvc on VcReg then you can do anything .
[Windows 10 Mobile] Enderneer:
I think they do check the RAM (at least for the latest Redstone builds).
[Windows 10 Mobile] dudeluv:
I followed the instructions, I didn't let the store update, ect....It all worked, I did restore the NDTKSvc on VcReg and was able to change the registry, I think it has something to do with the ram only being at 512

---------- Post added at 04:41 PM ---------- Previous post was at 04:30 PM ----------

They must cause it will not update. Is stuck at 107

I changed PhoneManufacturer

PhoneManufacturerModelName

PhoneModelName

PhoneHardwareVariant

I also tried this:

HKLM/SOFTWARE/OEM/Nokia/Variant/BSPRelease

HKLM/SOFTWARE/OEM/Nokia/Variant/ConfigurationID

I used the info from here, http://www.lumiafirmware.com

for the ......Lumia 640 XL LTE, Lumia 640 LTE, Lumia 950 XL

I set the insiders preview to fast and slow. Just cannot get it too update.:crying:
[Windows 10 Mobile] ngame:
not related to ram and not related to CPU model and even not related to both of them .

L920 has 1 GB Ram -> Boot loop

L1020 has 2 GB Ram -> Boot loop

L630 has 512 MB Ram and snapdragon -> boot loop

HTC One M8 1 GB Ram and snapdragon -> boot loop
[Windows 10 Mobile] Swordfishx86:
[MENTION=4542506]ngame[/MENTION]: dudeluv was talkin bout not even being given an update ...
[Windows 10 Mobile] dudeluv:
That is correct. Stuck after step 5 "check for the update and plug your device to charge"
[Windows 10 Mobile] raghulive:
i think , Microsof MDG wrote "Simple Boot loop code for redstone build >=14327"

if(processor == Snapdragon S4 || Snapdragon S4 plus)
{

System.bootLoop();

}

if (processor == Snapdragon 801 && RAM.value < 3072000000*8)
{

System.bootLoop();

}

else
{

System.load();

}
[Windows 10 Mobile] EmanuelManole:
Has anyone found a solution for the freezing start screen on the lumia 1320 ?
[Windows 10 Mobile] ngame:
It's a real stupid work to do on an operating system . and I think it should be 100% wrong . Why ? because lumia Icon could get it without boot loop .

I'm sure they did changed some registry changes or some Path changes to load system files that they didn't apply on unsupported phones .
[Windows 10 Mobile] raghulive:
updates can be downloaded and installed(Migrated) in unsupported devices with registry changes ,but next boot will check direct hardware(processor) and RAM to allow to load OS.they can't check more with in that short time of boot-loop.

Lumia Icon == || Lumia 930 ||(supported device) except carrier locked

they throw all devices with preloaded windows phone 8.0 in to Threshold Bin (before 2014 devices)

one & only device that escape from this ****ty bin is Lumia 1520

all supported Devices Windows phone 8.1(Base OS)

the above all Lumia story

HTC One M8 windows, is a high end device ,but still in boot loop,HTC had no interest on getting Redstone on their devices

,initially BLU devices are not in supported list ,even though they had newer processor(SD200)

but BLU did a great job to make their deices in Supported List

because these old supported devices need Firmware update in some point ,so they don't want to take burden of this,in between they need to fix issues with Redstone builds for unsupported devices.

in future Redstone PRELOADED devices may come with 64bit OS with SD830 , with 8gb Ram,

for RS4 ,preset supported devices will get in to boot loop.

this is all Microsoft MDG group stupid decision,at least we All should have option try Redstone ,user will stop updating when device is unable to use at particular build.
[Windows 10 Mobile] Swordfishx86:
[MENTION=4542506]ngame[/MENTION] [MENTION=6420856]raghulive[/MENTION] ... speculation? or analyzed disassembly? :p *scnr*

i force myself to believe that its just a bug in recent builds that eventually gets fixed. hope brave souls still keep testing new upcoming redstone builds for a change in behaviour *prays*
[Windows 10 Mobile] slyronit:
I got the boot loop, rolled back to 8.1., then enrolled into slow ring and am on the latest slow ring build.

Really hope future Redstone builds fix this.
[Windows 10 Mobile] raghulive:
we need to see next Redstone Slow ring Build(should be >=14327),if it escapes from boot loop,we all happy, otherwise we are forcedly limited to TH2 or 14295.
[Windows 10 Mobile] TristanLeBoss:
Has someone tried to install a bootlooping version, modify the BCD file on the EFIESP parition in order to "Enable boot logging"? This way we could fint out who is the culprit.

The flog file will be named ntbtlog.txt or bootlog.txt and should be found in the WIndows folder eitheir in the EFIESP partition or the MAINOS one.
[Windows 10 Mobile] dape16:
Is it really possible to access these partitions through mass storage mode when the phone is just boot looping?
[Windows 10 Mobile] ADeltaX:
Yes.
[Windows 10 Mobile] SalaarZahid:
Hi, guys! First of all thanks to all the older and experienced members who are Working right now to make this hack work again! Secondly I don't know if this would help much but just a speculation;

In the 143xx builds Microsoft Introduced a new way to get the insider builds. From the settings menu. In the first 143xx build they released only a husk of it. Maybe it wasn't a husk at all. Maybe in that part of the OS they wrote a code/module etc to prevent phones from upgrading. So If someone has the first 143xx build we can see what they have added in the code on that specific part of the OS. Hope my observation might help in someway. :) BEST OF LUCK GUYS!
[Windows 10 Mobile] fer_cabr:
Build 14332 is now available for Lumia Icon.
[Windows 10 Mobile] raghulive:
We can't see or modify code of development OS,you can't decompile update package file,that's not done by normal IDE,as you need to break lot of security/signature/authentication barriers.even if we see and modify total update package will be corrupted

Sent from mTalk
[Windows 10 Mobile] SalaarZahid:
Hmmm then I guess all of this now rests upon luck whether the next builds will allow us to go on or not. Well I'm certainly hoping for it. And also thanks for the information [MENTION=6420856]raghulive[/MENTION]
[Windows 10 Mobile] vlad6:
Anyone tryed InteropToolsApp_0.0.2.0 ?? I'm wondering with this new version if you need to go back to 8.1 to edit the registry....
[Windows 10 Mobile] dape16:
Boot logs

I have catched boot logs from 10586 (working) and 14332 (boot loop) tonight but I have not had the time to examine them, but at first sight I can't find anything suspicious in the 14332 log. I also tried booting 14332 with an EFI partition from 10586 but it didn't work either. I have the log files attached here.
[Windows 10 Mobile] TristanLeBoss:
14332 boot is aborted. It stops after loading "NokiaEnergyDriver.sys"....

I may be totaly wrong but, because of the OneCore architecture, I think there is a crash and instead of displaying a BSOD (blue screen), the phone reboots.

TODO: Can someone dump the "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CrashControl" key of a phone registry?

In this key, there should be an "AutoReboot" REG_DWORD value, a "LogEvent" REG_DWORD value, a "CrashDumpEnabled" REG_DWORD value which need to be set to 0 for the first one and 1 for the second and the third.

TODO: Can someone check if the folder "\Windows\system32\winevt\logs" exists and contains files? (either on MainOS or EFIESP partition) Same reflexion as before: because of OneCore architecture, Windows 10 Mobile should behave like Windows 10 for PC and so, may feature a logging system. On a PC, you can access it through the "Event Viewer" under "Administrative Tools". We should be able to open the log from a phone with a PC.
[Windows 10 Mobile] akhilkalwakurthy:
Differences between 10586 and 14332 log files

I found these basic differences between those files. I've pointed them out in the following file. (sorry, I can't post links here. Please copy the URL below)

URL = "https://onedrive.live.com/redir?resid=E724AC567CCD44BE!74459&authkey=!AOh-f2dOtk7Db5M&ithint=file%2ctxt"
[Windows 10 Mobile] TristanLeBoss:
Thanks.

So, yes, the phone (like a PC is by default) is set to restart on error (AutoReboot = 1) [ https://technet.microsoft.com/en-us/library/cc976049.aspx ] instead of showing a BSOD. I can easily understand why ;) Imagine the face of the customer...

It's also set to save a small memory dump in case of crash (CrashDumpEnabled = 3) [ https://technet.microsoft.com/en-us/library/cc976050.aspx ].

So, if the bootloop is due to a crash, we should be able to prevent the reboot (AutoReboot = 0) to see the error and save a crash dump (CrashDumpEnabled = 1) by editing the registry.
[Windows 10 Mobile] ngame:
OK Guys, Seems the end of support for our old devices processors is true.

Microsoft recently updated the minimum hardware requirements for windows 10 mobile .

No more support for 512 MB of Ram , 4GB of storage and MSM8960 (QC S4 Plus like Lumia 920 processor)

at least 1GB of RAM and 8GB of non-removable flash storage. The following Qualcomm processors are supported,

◾MSM8994, MSM8992, MSM8952, MSM8909, MSM8208, MSM8996, MSM8953

read more on MSPowerUser
[Windows 10 Mobile] Kenny7:
which one is used in Lumia 1020? I think its the same as 920, just more RAM, right?
[Windows 10 Mobile] dape16:
MSM8960.
[Windows 10 Mobile] TTMaster:
Does anyone have the xap FM Radio?

:angel:
[Windows 10 Mobile] Enderneer:
That's the list of SOCs in devices that run Windows 10 mobile (i.e. devices that come with Windows 10 mobile pre-installed). The supported SOCs of devices that can be upgraded to Windows 10 mobile are listed in table 6 on the minimum hardware requirements page: https://msdn.microsoft.com/en-us/library/windows/hardware/dn915086(v=vs.85).aspx

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

The S4 is still in the list of supported SOCs.