1. WindowsSoccerCentral's Avatar
    Help! WM10 14295 crashed my 1520. Unfortunately, I did the WM10 technical preview because it was the only way to keep my 1520 from 'bugging' out after I dropped it (primary phone). I was fine for a long while. I did this update and I crashed and burned. I was thinking of using the recovery tool...but that will take me back to w8.1?
    Last edited by WindowsSoccerCentral; 03-26-2016 at 10:07 PM.
    03-26-2016 04:25 PM
  2. ven07's Avatar
    Eh not sure I follow your logic but ok. Try a hard reset and don't restore any backups. Check if your issues are still there.

    The answer to your question: yes using wprt will take you back to 8.1 and from there you can upgrade back to 164 by selecting slow ring
    03-26-2016 06:18 PM
  3. charlatan1978's Avatar
    Maybe, just maybe your phone is damaged after you 'dropped it'.
    ven07 likes this.
    03-26-2016 07:43 PM
  4. WindowsSoccerCentral's Avatar
    Hi Charlatan... I would've said yes back in October when I dropped it...but quite a bit of time passed and, until recently, it has been working AhhhMazing!
    03-26-2016 10:06 PM
  5. WindowsSoccerCentral's Avatar
    Sorry...should explain. In October, I dropped the phone. I was lucky when I purchased because my 1520 did not display any 'glitchy' behavior some had reported on the web. When I dropped it...the "ghost in the machine" was awakened. I'm on the insider program and took a gamble that if I upgraded the phone with a different OS...maybe it would alter the "ghost". Ironically...that is exactly what happened. My phone went back to "normal". Each build made it stronger and more familiar to original behavior, responding positively and glitch-free. It's weird... but it was a gamble. It saved me from having to buy a new phone before the end of my contract. I did the recent update...#14291 and apps, basic phone operations, you name it, just didn't work. The next day, #14295 was released with the belief it was going to 'repair' the issues...and it just made it worse for me. That's why I needed help.
    03-26-2016 10:07 PM
  6. ven07's Avatar
    did you hard reset after the upgrade? like I said previously, do that and check again. Btw it seems that you've been in the fast ring most of the time. The fast ring will mostly provide "buggy" builds. So if you can't point to anything that has to do with a hardware malfunction that it most likely just software, which a hard reset could resolve.

    Also MS has yet to release actual firmware updates for the non-w10m phones. So far only the 950/XL have gotten firmware. I have seen a lotof 830/735/ users complaining about glitches lately. Some of them just upgraded to 164 and were having issues, while others are idd in the fast ring. So your case isn't unique.

    The hard reset could help or it won't. Like one of my colleagues pointed out: "windows 10 is volatile" so basically it has moods lol
    03-26-2016 10:27 PM
  7. shenandoah's Avatar

    To get back to 10586.1564 you'll need to reset to 8.1 using the Windows Device Recovery Tool. Once at 8.1, choose the slow ring on Windows Insider. The first update will bring you to 10586.107, the next update will bring you to 10586.164.

    If you choose the fast ring, the first update will bring you to 10586.107, then to 14295.

    I did this yesterday after 14295 wreaked havoc on my Lumia 640 dual sim...

    03-27-2016 07:16 AM

Similar Threads

  1. Why can't I play HBO GO on my Surface RT anymore?
    By Windows Central Question in forum Microsoft Surface Laptop
    Replies: 1
    Last Post: 11-30-2016, 06:24 PM
  2. Why is my Lumia 720 battery draining while charging?
    By Windows Central Question in forum Windows Phones
    Replies: 1
    Last Post: 08-12-2016, 06:21 PM
  3. Cannot roll back to wp 8.1
    By Windows Central Question in forum Ask a Question
    Replies: 6
    Last Post: 03-26-2016, 11:33 PM
  4. How to use DISM command-line utility to repair a Windows 10 image
    By WindowsCentral.com in forum Windows Central News Discussion & Contests
    Replies: 0
    Last Post: 03-26-2016, 04:20 PM