WFAv7_Installer
WFAv7_Installer copied to clipboard
RedGreenBlue09
Lumia 520 freezes on bootup.
It boots to the boot manager, but freezes when the spinning dots loads up. Anything I can do?
Hi. Try connecting the phone to WinDBG (download from MS Store) on PC.
Attach to kernel > USB then type in target name WOATARGET. After this, reboot the phone. When it says connected, click Go. Send it's output to me.
I also suspect low memory causing the issue, so consider mounting it's registry and enable the page file.
Im stuck, am i supposed to up click on the windows 10 (debugger) thing?
************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true
-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true
>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds
************* Waiting for Debugger Extensions Gallery to Initialize **************
>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.031 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 36
Microsoft (R) Windows Debugger Version 10.0.25921.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Using USB for debugging
Waiting to reconnect...
USB: Write opened
Connected to Windows 10 15035 ARM (NT) Thumb-2 target at (Tue Nov 28 17:45:37.678 2023 (UTC - 6:00)), ptr64 FALSE
Kernel Debugger connection established.
Symbol search path is: srv*
Executable search path is:
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_MMPTE_TRANSITION ***
*** ***
*************************************************************************
Windows 10 Kernel Version 15035 MP (1 procs) Free ARM (NT) Thumb-2
Edition build lab: 15035.0.armfre.rs2_release.170209-1535
Kernel base = 0x82857000 PsLoadedModuleList = 0x82a64438
System Uptime: 0 days 0:00:00.362
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_MMPTE_TRANSITION ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_MMPTE_TRANSITION ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_MMPTE_TRANSITION ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_MMPTE_TRANSITION ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_MMPTE_TRANSITION ***
*** ***
*************************************************************************
BGFX Display Ready Time (ms): 52270
BGFX Secondary Logo Bitmap Display Time GOAL (ms): 57270
EXWORKER: worker exit with system affinity set, worker routine 883C5629, parameter 87072B2C, item 87072B2C
KDTARGET: Refreshing KD connection
BGFX Secondary Logo Bitmap Display Time (ms): 57298
DMUX::BamMuxRegGetNumBuffers:2319: Number of buffers = 256
pil: The ELF image failed initialization: \SYSTEMROOT\SYSTEM32\QCADSP8930.MBN
ST: Welcome To Synaptics
ST: OpenIOTarget Entry
ST: OpenIOTarget Exit
ST: Starting bring up sequence for the controller
ST: Setting reset gpio pin to low
ST: Waiting...
ST: Setting reset gpio pin to high
ST: Waiting...
pil: The ELF image failed initialization: \SYSTEMROOT\SYSTEM32\QCWCNSS8930.MBN
ST: Done
ST: Error retrieving registry configuration - STATUS:C0000034
ST: Error reading registry config, using defaults! - STATUS:C0000034
ST: call to TchBklOpenHwnDriver
ST: Discovered function $34
ST: Discovered function $1
ST: Discovered function $11
ST: Discovered function $54
ST: Discovered function $31
ST: Discovered function $1a
ST: Discovered function $55
ST: Discovered function $51
ST: Discovered 8 RMI functions total
ST: founded 1 interupts for f11. setting mast to 4
ST: founded 1 interupts for f1a. setting mast to 10
ST: Max Fingers Count. Value is 5
ST: Error finding idle notification request in IdleQueue:0x6FD1C870 - STATUS:8000001A
ST: Created hidReportDescBuffer on 9032E9E0
ST: Set X=480 in 9032EA06
ST: Set Y=800 in 9032EA1B
ST: Set X=480 in 9032EA49
ST: Set Y=800 in 9032EA5E
ST: Set X=480 and Y=800 in hidReportDescriptor
ST: Unexpected -- no interrupt status bit set
Capacity:1, FullChargedCapacity:1350, Voltage:3225, Rate:0
LumiaButtonsGPIO: LumiaButtonsGPIOProbeResources Entry
LumiaButtonsGPIO: Found Interrupt resource id=0 index=0
LumiaButtonsGPIO: Found Interrupt resource id=1 index=2
LumiaButtonsGPIO: Found Interrupt resource id=2 index=4
LumiaButtonsGPIO: Found Interrupt resource id=3 index=6
LumiaButtonsGPIO: Found Interrupt resource id=4 index=8
LumiaButtonsGPIO: Beginning to create interrupts
LumiaButtonsGPIO: Created Interrupt
LumiaButtonsGPIO: Created Interrupt
LumiaButtonsGPIO: Created Interrupt
LumiaButtonsGPIO: Created Interrupt
LumiaButtonsGPIO: Created Interrupt
LumiaButtonsGPIO: LumiaButtonsGPIOProbeResources Exit: 0
ST: Error finding idle notification request in IdleQueue:0x6FCBCFE8 - !STATUS!
LumiaButtonsGPIO: OnD0EntryPostInterruptsEnabled Entry
LumiaButtonsGPIO: OnD0EntryPostInterruptsEnabled Exit
NRSDRIVER::NRSDebugPrintState (ERR): Key \Registry\Machine\Software\Microsoft\Shell\OOBE doesn't exist !!!!
NRSDRIVER::NRSDebugPrintState (ERR): Key \Registry\Machine\Software\OEM\Nokia\Multivariant\Color doesn't exist !!!!
NRSDRIVER::NRSDebugPrintState (ERR): Key \Registry\Machine\Software\Microsoft\Shell\OEM\Wallpaper doesn't exist !!!!
NRSDRIVER::NRSDebugPrintState (ERR): Key \Registry\Machine\Software\Microsoft\Windows\CurrentVersion\Control Panel\Theme doesn't exist !!!!
NRSDRIVER::NRSSetDeviceColor (ERR): Getting OOBE done state failed.
+--BGFX-REPORT-----------------+
| |
| DisplayMode: 480x 800x32 |
| LogoSize: 1152054 |
| |
| ProgressProlog: 0 |
| ProgressFrames: 0 |
| ProgressMemory: 193248 |
| ProgressLow: 0 |
| ProgressHigh: 0 |
| ProgressManual: 0 |
| ProgressTotal: 0 |
| |
| FadeProlog: 0 |
| FadeFrames: 0 |
| FadeMemory: 0 |
| FadeIo: 0 |
| FadeCpu: 0 |
| FadeLow: 0 |
| FadeHigh: 0 |
| FadeOverlap: 26925785 |
| FadeTotal: 0 |
| |
| AnimationTotal: 0 |
| |
| ResidentSize: 117808 |
| |
| CompressBitmapsCPU: 0|
| |
+------------------------------+
NRSDRIVER::NRSDebugPrintState (ERR): Key \Registry\Machine\Software\Microsoft\Shell\OOBE doesn't exist !!!!
NRSDRIVER::NRSDebugPrintState (ERR): Key \Registry\Machine\Software\OEM\Nokia\Multivariant\Color doesn't exist !!!!
NRSDRIVER::NRSDebugPrintState (ERR): Key \Registry\Machine\Software\Microsoft\Shell\OEM\Wallpaper doesn't exist !!!!
NRSDRIVER::NRSDebugPrintState (ERR): Key \Registry\Machine\Software\Microsoft\Windows\CurrentVersion\Control Panel\Theme doesn't exist !!!!
NRSDRIVER::NRSSetDeviceColor (ERR): Getting OOBE done state failed.
NRSDRIVER::NRSDebugPrintState (ERR): Key \Registry\Machine\Software\Microsoft\Shell\OOBE doesn't exist !!!!
NRSDRIVER::NRSDebugPrintState (ERR): Key \Registry\Machine\Software\OEM\Nokia\Multivariant\Color doesn't exist !!!!
NRSDRIVER::NRSDebugPrintState (ERR): Key \Registry\Machine\Software\Microsoft\Shell\OEM\Wallpaper doesn't exist !!!!
NRSDRIVER::NRSDebugPrintState (ERR): Key \Registry\Machine\Software\Microsoft\Windows\CurrentVersion\Control Panel\Theme doesn't exist !!!!
NRSDRIVER::NRSSetDeviceColor (ERR): Getting OOBE done state failed.
NRSDRIVER::NRSDebugPrintState (ERR): Key \Registry\Machine\Software\Microsoft\Shell\OOBE doesn't exist !!!!
NRSDRIVER::NRSDebugPrintState (ERR): Key \Registry\Machine\Software\OEM\Nokia\Multivariant\Color doesn't exist !!!!
NRSDRIVER::NRSDebugPrintState (ERR): Key \Registry\Machine\Software\Microsoft\Shell\OEM\Wallpaper doesn't exist !!!!
NRSDRIVER::NRSDebugPrintState (ERR): Key \Registry\Machine\Software\Microsoft\Windows\CurrentVersion\Control Panel\Theme doesn't exist !!!!
NRSDRIVER::NRSSetDeviceColor (ERR): Getting OOBE done state failed.
NRSDRIVER::NRSDebugPrintState (ERR): Key \Registry\Machine\Software\Microsoft\Shell\OOBE doesn't exist !!!!
NRSDRIVER::NRSDebugPrintState (ERR): Key \Registry\Machine\Software\OEM\Nokia\Multivariant\Color doesn't exist !!!!
NRSDRIVER::NRSDebugPrintState (ERR): Key \Registry\Machine\Software\Microsoft\Shell\OEM\Wallpaper doesn't exist !!!!
NRSDRIVER::NRSDebugPrintState (ERR): Key \Registry\Machine\Software\Microsoft\Windows\CurrentVersion\Control Panel\Theme doesn't exist !!!!
NRSDRIVER::NRSSetDeviceColor (ERR): Getting OOBE done state failed.
NRSDRIVER::NRSDebugPrintState (ERR): Key \Registry\Machine\Software\Microsoft\Shell\OOBE doesn't exist !!!!
NRSDRIVER::NRSDebugPrintState (ERR): Key \Registry\Machine\Software\OEM\Nokia\Multivariant\Color doesn't exist !!!!
NRSDRIVER::NRSDebugPrintState (ERR): Key \Registry\Machine\Software\Microsoft\Shell\OEM\Wallpaper doesn't exist !!!!
NRSDRIVER::NRSDebugPrintState (ERR): Key \Registry\Machine\Software\Microsoft\Windows\CurrentVersion\Control Panel\Theme doesn't exist !!!!
NRSDRIVER::NRSSetDeviceColor (ERR): Getting OOBE done state failed.
NRSDRIVER::NRSDebugPrintState (ERR): Key \Registry\Machine\Software\Microsoft\Shell\OOBE doesn't exist !!!!
NRSDRIVER::NRSDebugPrintState (ERR): Key \Registry\Machine\Software\OEM\Nokia\Multivariant\Color doesn't exist !!!!
NRSDRIVER::NRSDebugPrintState (ERR): Key \Registry\Machine\Software\Microsoft\Shell\OEM\Wallpaper doesn't exist !!!!
NRSDRIVER::NRSDebugPrintState (ERR): Key \Registry\Machine\Software\Microsoft\Windows\CurrentVersion\Control Panel\Theme doesn't exist !!!!
NRSDRIVER::NRSSetDeviceColor (ERR): Getting OOBE done state failed.
NRSDRIVER::NRSDebugPrintState (ERR): Key \Registry\Machine\Software\Microsoft\Shell\OOBE doesn't exist !!!!
NRSDRIVER::NRSDebugPrintState (ERR): Key \Registry\Machine\Software\OEM\Nokia\Multivariant\Color doesn't exist !!!!
NRSDRIVER::NRSDebugPrintState (ERR): Key \Registry\Machine\Software\Microsoft\Shell\OEM\Wallpaper doesn't exist !!!!
NRSDRIVER::NRSDebugPrintState (ERR): Key \Registry\Machine\Software\Microsoft\Windows\CurrentVersion\Control Panel\Theme doesn't exist !!!!
NRSDRIVER::NRSSetDeviceColor (ERR): Getting OOBE done state failed.
Im a bit of a newbie to this type of modification, I'm just starting to get my IT credits for college.
it crashed? WER/CrashExp:363: ERROR Failed to create the process "C:\Windows\system32\WerFault.exe", cmdline "C:\Windows\system32\WerFault.exe -u -p 3656 -s 2208", creationflags 525312, HRESULT 800705AF
Also how do i get access to the storage?
I think low RAM is the issue. Try increasing the page file size.
You can access phone storage via Mass Storage Mode.
Also how do i get access to the storage?
I think low RAM is the issue. Try increasing the page file size.
You can access phone storage via Mass Storage Mode.
So how do i get into mass storage mode? its usually done by going into WPinternals, but it doesnt show up on wpinternals.
Also how do i get access to the storage?
I think low RAM is the issue. Try increasing the page file size.
You can access phone storage via Mass Storage Mode.
If its possible i can put the pagefile on a SD Card, the storage space is incredibly small
Also how do i get access to the storage?
I think low RAM is the issue. Try increasing the page file size.
You can access phone storage via Mass Storage Mode.
Ive ran windows 10 on 512MB fine, so this is genuinely surprising for me lol
So how do i get into mass storage mode? its usually done by going into WPinternals, but it doesnt show up on wpinternals.
In WPinternals: Click interrupt boot process, then reboot the phone.
If its possible i can put the pagefile on a SD Card, the storage space is incredibly small
A SD Card as it's marked as a removable storage, but you cannot put the page file on a removable storage AFAIK. You don't know the drive letter of the SD Card anyway.
There is a thing called ReadyBoost for removable storage which can help reducing RAM usage, you can enable that after OOBE.
Ive ran windows 10 on 512MB fine, so this is genuinely surprising for me lol
It worked on 512 MB thanks to the page file. Windows 10 ARM somehow fails to create the page file automatically, so you need to add it manually.
So how do i get into mass storage mode? its usually done by going into WPinternals, but it doesnt show up on wpinternals.
In WPinternals: Click
interrupt boot process, then reboot the phone.If its possible i can put the pagefile on a SD Card, the storage space is incredibly small
A SD Card as it's marked as a removable storage, but you cannot put the page file on a removable storage AFAIK. You don't know the drive letter of the SD Card anyway.
There is a thing called ReadyBoost for removable storage which can help reducing RAM usage, you can enable that after OOBE.
Ive ran windows 10 on 512MB fine, so this is genuinely surprising for me lol
It worked on 512 MB thanks to the page file. Windows 10 ARM somehow fails to create the page file automatically, so you need to add it manually.
Okay! and I don't mind! I appreciate your help greatly sir!
Also, how do i make a pagefile? Lol...
I mentioned that here:
I mentioned that here:
- [ ] I did it lol, im just gonna wipe win10 and put WinPE or sum on it. im tryna unlock it rn
The best I can predict about this issue is that we have insufficient RAM because the page file for some reason fails to be created automatically. Unfortunately, I don't own the 520 so I can't test it myself. I'll consider making a page file fix instead.
oh damn, I was also getting this issue but THERE IS A FIX. disabling testsigning makes it work!? but then touch and stuff is screwed up. it seems to be a driver issue somehow and im not sure how this could be fixed personally. windows boots to the oobe on my 520 when testsigning is off
im gonna flash my 520 (it has rt on it) and try fixing this issue since it happened twice in a row and i sorta gave up :P good luck to you
I think if you disable testsigning, less drivers load hence less RAM used so it don't freeze.
would make sense, but its rather odd and CurrentControlSet doesnt seem to yet exist when windows freezes, maybe letting it get to oobe will make this work? controlset001 does exist and applying the mod there it still shows the frozen dots (windbg is still responding with the hardware buttons)
disabling the registry settings to make windows boot to the regular logonui freezes on a total black screen with the backlight illuminated. might try reading the logs after clearing windbg and rebooting - the phone is still on and responding but windows at least gets somewhere now it seems. no user account to log onto though if logonui does work, but i expect then replacing the cmdline would let us use osk to make a user or just make a batch file on pc to do it
custommadewindbglog.txt windows gets this far according to windbg (might have missed ntoskrnl doing some stuff tho, time was tight between the usb write starting and NT starting)
SOLVED IT! my pagefile was too small, set it to minimum 1024 max 2048 and win10 booted like a charm. thank you!!