Presumptive Nominee for AU 10.0.14393.5 Discussion (Redstone Branch, Inactive)

[mtf1380]

Re: Presumptive Nominee for AU 10.0.14393.5 Discussion (Redstone Branch; Fast, Slow & Release Rings)

Groove over Bluetooth is non existing; cut out yesterday during a run, and I cannot get to re-engage, went to another music player for todays run, and it cut out just like the Groove Player did before I lost it completely. Very annoying.

On another note:
> the little directional indicator on the Maps app is pretty cool.
> OneNote is still worthless on my 950XL; doesn't update a page, does retain the info from prior syncs (this feature IS the reason that I have a Windows Phone).

ALL the above has been reported via Feedback Hub.

 

[mtf1380]

Re: Presumptive Nominee for AU 10.0.14393.5 Discussion (Redstone Branch; Fast, Slow & Release Rings)

build 14393.67 downloading NOW!

 

[Shamshi-Adad]

Re: Presumptive Nominee for AU 10.0.14393.5 Discussion (Redstone Branch; Fast, Slow & Release Rings)

build 14393.67 downloading NOW!

What the....it's available to me too on Verizon. Now I gotta git the dog, go to McDonalds, git some cheeseburgers and sit in the parking lot and use their wifi. :winktongue:

Peace. Alan
MS Lumia ICON 929 [Win10 M, Insider Preview, Redstone 14393.5]
EDIT:
MS Lumia ICON 929 [Win10 M, Insider Preview, Redstone 14393.67] :winktongue:

 

[RumoredNow]

All Insider Rings (Fast, Slow, Release) have now moved on to build 14393.67: http://forums.windowscentral.com/wi...redstone-branch;-fast-slow-release-rings.html

Please continue on here for 14393.5 only...

 

[Albatross2]

I have a 950 dual sim running 393.5 software. The update to 393.67 is failing with error code 0xd0000008 and I can find nothing valuable on the internet related to this error code. I have done multiple soft resets with no effect. I finally resolved to do a hard reset and that is failing as well with the message "We couldn't reset the phone. Try again later.".

Looks like I may be stuck in a dead end. Considering the WDRT at this point.

 

[RumoredNow]

Considering the WDRT at this point.

0xd0000008 seems to point to corrupted registry and the failed reset would appear as confirmation.

WDRT is your best course at this point.

 

[Albatross2]

WDRT is your best course at this point.

WDRT also fails and says it cannot recovery my device right now. I'm going to try putting my phone in flash mode and using WDRT.

 

[RumoredNow]

WDRT also fails and says it cannot recovery my device right now. I'm going to try putting my phone in flash mode and using WDRT.

My experience and anecdotal evidence from users reporting in says do the steps opposite what Microsoft says.

Microsoft: "Connect to WDRT and then enter flashing mode."

Me: "Enter flashing mode, connect to USB and open WDRT"

 

[Albatross2]

Success with WDRT using flash mode. Now I just have to get the phone up to the latest insider before resetting and trying my backup.

 

[Albatross2]

Now I'm really stuck. I flashed back to 10586.318 with WDRT, but I get the same error code 0xd0000008 when trying to upgrade from there. The first time I tried to go windows insider first. The second time I flashed again and just tried to update on the 10586 branch, same error.

I'm sure at this point it is my device and not the 393.5 software that is the culprit.

 

[PGrey]

Now I'm really stuck. I flashed back to 10586.318 with WDRT, but I get the same error code 0xd0000008 when trying to upgrade from there. The first time I tried to go windows insider first. The second time I flashed again and just tried to update on the 10586 branch, same error.

I'm sure at this point it is my device and not the 393.5 software that is the culprit.

I got stuck like this, and went into my device-management console on my Live login (PC, tablet, whatever) and removed my reset-protection.
That fixed it for me, I think it was 14393.5 where I got stuck, with a horrendous battery issue (I'm usually anti-reset), but needed to for this, phone was unusable.
After that, my phone (950XL) was able to reset, cleanly, and I didn't get that error about being locked, and I'm running 14393.67 now, without the issues.