WOA-Project / WOA-Deployer-Lumia

Making your Lumias great again!
MIT License
481 stars 71 forks source link

[950XL] 18362 Unexpected restart loop on first time setup causing setup failure. #29

Closed ghost closed 5 years ago

ghost commented 5 years ago

I tried installing 18362.86 however I get an error trying to start it, "The computer started unexpectedly or encountered an unexpected error. Windows installation cannot proceed. To install windows, click "OK" to restart the computer, then restart the installation." It just shows that message every time and is stuck on a loop.

BelleNottelling commented 5 years ago

You shutdown your phone before the install finished, reinstall Windows and try again. After the screen goes black wait and eventually you should see windows loading and starting to install, if you turn it off before it's done you'll get that error message and have to start again

ghost commented 5 years ago

Sorry but I didn't touch it after I rebooted into normal mode. It went to a blank screen during the boot then it rebooted itself after just 2 mins. I didn't shut it down at all.

BelleNottelling commented 5 years ago

Try again then, it's not a perfect process. If that doesn't work try a different build, I'll tell you the build I used later if that doesn't work for you

ghost commented 5 years ago

I also tried 17763.475 and it did the exactly the same thing.

BelleNottelling commented 5 years ago

IMG_20190508_212512 Did this yesterday, took a few attempts, but it does work. How is the battery on your device? A bad battery can cause random reboots and shut downs.

tkiapril commented 5 years ago

Logs? The developers can't help you if they don't know what's going south in your deployment.

ghost commented 5 years ago

Well that's the thing. The deployment was successful yet the install fails on the phone itself.

tkiapril commented 5 years ago

Your best bet still is to upload the logs. The logs contain the nitty gritty details about the deployment, and it's not just pass/fail like if it's either way or other. I'm not a dev for this project, but without the log files the devs will never know what's going wrong in your case and won't be able to help you.

BaRRaKudaRain commented 5 years ago

Maybe you should try another Windows 10 build? 16299 RS3 for example. Later builds may cause some problems.

On Thu, May 9, 2019 at 2:30 AM raidensnake notifications@github.com wrote:

I tried installing 18362.86 however I get an error trying to start it, "The computer started unexpectedly or encountered an unexpected error. Windows installation cannot proceed. To install windows, click "OK" to restart the computer, then restart the installation." It just shows that message every time I try to restart it.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/WOA-Project/WOA-Deployer-Lumia/issues/29, or mute the thread https://github.com/notifications/unsubscribe-auth/AHDVDWFKEZGRFA6TYCOHZLDPUNO73ANCNFSM4HLV7AEA .

--

An outsider, The BaRRaKudaRain

carues commented 5 years ago

I had the same message with builds creatingISO_18362.86_pt-br_arm64_professional.cmd and creatingISO_17763.349_pt-br_arm64_Professional.cmd . The error shows in the phone screen after applied the windows image as shown in the attached file (Is in Brazilian Portuguese) .

20190510_190519

carues commented 5 years ago

Where I find the logs in the cellphone to post here?

ghost commented 5 years ago

+1 on @carues The deploy logs themselves don't show any issues.

ghost commented 5 years ago

deploy.txt There's the recent deploy log.

SuperJMN commented 5 years ago

The deployment was successful. That's why the log doesn't have any error inside.

SuperJMN commented 5 years ago

BTW, I'm closing this issue since it's not Deployer related, but it faills into the WOA or Drivers or EUFI side. Sorry guys. Deployer responsibility is to deploy, only.

SuperJMN commented 5 years ago

One final comment. The boot loop is normally a driver issue that can be fixed redeploying. Try it to see if that helps :)

ghost commented 5 years ago

I tried that several times @SuperJMN and it made no difference whatsoever.

SuperJMN commented 5 years ago

Can you try with another build, for example 18890 or 18894?

ghost commented 5 years ago

I tried those as well and got the same problem.

carues commented 5 years ago

I tried one more time with build creatingISO_17763.349_pt-br_arm64_Professional.cmd but in this time I didn't disconnect the cellphone from the computer as the Woa.deployed says after end the process. And it works!!

Obter o Outlook para Androidhttps://aka.ms/ghei36


From: raidensnake notifications@github.com Sent: Saturday, May 11, 2019 5:47:17 AM To: WOA-Project/WOA-Deployer-Lumia Cc: carues; Mention Subject: Re: [WOA-Project/WOA-Deployer-Lumia] [950XL] 18362 Unexpected restart loop on first time setup causing setup failure. (#29)

I tried those as well and got the same problem.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/WOA-Project/WOA-Deployer-Lumia/issues/29#issuecomment-491496566, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AJPXODRJAI5YQOBKVDEOMNDPU2I2LANCNFSM4HLV7AEA.

BaRRaKudaRain commented 5 years ago

Seems that WOA deployer deployed the installer image, not the install.wim file. So that's the reason that it cannot continue.

An outsider, the BaRRaKudaRain

-----Original Message----- From: "raidensnake" notifications@github.com Sent: ‎5/‎10/‎2019 4:09 PM To: "WOA-Project/WOA-Deployer-Lumia" WOA-Deployer-Lumia@noreply.github.com Cc: "Subscribed" subscribed@noreply.github.com Subject: Re: [WOA-Project/WOA-Deployer-Lumia] [950XL] 18362 Unexpected restartloop on first time setup causing setup failure. (#29)

Well that's the thing. The deployment was successful yet the install fails on the phone itself. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

SuperJMN commented 5 years ago

With normal usage, that cannot happen. The wim selecting dialog prompts specifically for “install.wim”, that IS the correct image.

Enviado desde Correohttps://go.microsoft.com/fwlink/?LinkId=550986 para Windows 10


De: Ilya Lapa notifications@github.com Enviado: Saturday, May 11, 2019 12:18:07 PM Para: WOA-Project/WOA-Deployer-Lumia Cc: José Manuel Nieto; Mention Asunto: Re: [WOA-Project/WOA-Deployer-Lumia] [950XL] 18362 Unexpected restart loop on first time setup causing setup failure. (#29)

Seems that WOA deployer deployed the installer image, not the install.wim file. So that's the reason that it cannot continue.

An outsider, the BaRRaKudaRain

-----Original Message----- From: "raidensnake" notifications@github.com Sent: ‎5/‎10/‎2019 4:09 PM To: "WOA-Project/WOA-Deployer-Lumia" WOA-Deployer-Lumia@noreply.github.com Cc: "Subscribed" subscribed@noreply.github.com Subject: Re: [WOA-Project/WOA-Deployer-Lumia] [950XL] 18362 Unexpected restartloop on first time setup causing setup failure. (#29)

Well that's the thing. The deployment was successful yet the install fails on the phone itself. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/WOA-Project/WOA-Deployer-Lumia/issues/29#issuecomment-491498663, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAXXHW7PEISFHA5X2SHRYI3PU2MN7ANCNFSM4HLV7AEA.

tkiapril commented 5 years ago

@BaRRaKudaRain What I see in your logs is that you are using uup converter to download the files and convert them. Try using uup-downloader available on gitlab if you aren't already. (I cannot link them here because I'm not sure about the legality, sorry.)

tkiapril commented 5 years ago

Btw, I guess that it is extremely unlikely that it might be the case, but make sure you use sources/install.wim, not boot.wim.

tkiapril commented 5 years ago

@BaRRaKudaRain sorry, seems like I mentioned the wrong person. That comment was supposed to go to @raidensnake .