[Edit: My 1520.3 has resurrected itself. Not bricked by 14322. I'll need to see how unstable.]

[Captain_Eric]

[Edit: It's not bricked. After having given up after trying "everything" over a couple of days, I plugged my 1520.3 in and it booted up just fine. Go figure.]

FWIIW: I had big problems when I upgraded to Redstone, 14xxx, from 8.1, battery drain, frequent crashes.

Eventually, it bricked my 1520.3.

I know that was the risk I took when I signed up for Insider, but be forewarned.

I'd strongly suggest saying on W10 production, i.e. 10586.xxx.

If anyone (RumoredNow?, who ha my same phone) has any ideas on how to revive my 1520.3, please let me know.

Posted via the Windows Central App for Android

 

[RumoredNow]

Re: Upgrade to Redstone 14322 bricked my 1520.3

Does the phone take a charge at all?

What are you seeing, BSOD?

Have you tried WDRT while in Flash Mode and using Device Not Detected for WDRT? http://forums.windowscentral.com/ge...ol-expanded-covers-more-oems.html#post3409280

 

[Captain_Eric]

Re: Upgrade to Redstone 14322 bricked my 1520.3

Does the phone take a charge at all?

What are you seeing, BSOD?

Have you tried WDRT while in Flash Mode and using Device Not Detected for WDRT? http://forums.windowscentral.com/ge...ol-expanded-covers-more-oems.html#post3409280

Thanks for getting back to me. Please see my edit above: It's alive.

And yes, previously I tried WDRT in all its ways.

Bottom line: I'm confused, but happy.

 

[RumoredNow]

Re: Upgrade to Redstone 14322 bricked my 1520.3

Please see my edit above: It's alive.

Adequate battery can make or break a Recovery.

Glad you are rocking and rolling.

You have the AT&T Model? If yes... Try Insider Release. It today went to 10586.318, but that is also matched by Production. Very stable point to hold at, IMHO. You could Insider to that and then go Production and wait it out. I would guess that AT&T will catch up soon. This makes 2 rounds of Production bug fix since Threshold went RTM.