Nokia Lumia 1520 bricked

[myrandex]

I just wanted to share some information that occurred this morning here. I bricked my Lumia 1520 with the developer preview program. I successfully updated the phone and I have to say WP 8.1 seems quite nice.

As part of my testing that I was trying to accomplish to see if issues with the WP 8 OS were fixed relating to SD card encryption I wanted to perform a factory reset. Upon factory resetting the phone to start from a blank slate, I received my first BSOD in WP (Achievement Unlocked!)

Anyways the error is:
(0% complete) Id you'd like to know more, you can search online later for this error: PROCESS1_INITIALIZATION_ERROR

I will attach a screenshot later. Tapatalk crashed last time I tried.

Jason Cook

Sent from my Nokia Lumia 920 using Tapatalk

 

[BIGPADDY]

Thanks for the information.

 

[liam-ward]

I've got a 1520 and I was JUST about to reset my phone after the update to start clean, I will avoid it until i hear anything else. Thanks

 

[NoRomBasic]

This could be bad. I just did a soft-reset on my Lumia 1520 after it could no longer launch the Music or Photos apps and now all I have is the BSOD/Unhappy face immediately after the ATT screen comes up.

 

[treetownal]

Also stuck on that same screen - Unlocked ATT 1020. I can't seem to escape the BSOD, nothing is responding.

 

[NoRomBasic]

Yep, it looks like I'm hosed. Can't get it to connect to Nokia CareSuite, can't force a flash, sucker doesn't respond to anything right now. Very, Very, Sad...

 

[treetownal]

Did you try holding power and playing with the volume rockers? It eventually got me out of the BSOD, although now the gears are spinning at about 5% without making progress (I have measured the progress bar using a piece of tape to see if it was going anywhere).

 

[NoRomBasic]

Did you try holding power and playing with the volume rockers? It eventually got me out of the BSOD, although now the gears are spinning at about 5% without making progress (I have measured the progress bar using a piece of tape to see if it was going anywhere).

I'll give it a shot. I can see I'll be playing with it for a while here. At least I can stuff my SIM in my "backup" 822 if it takes a while....

 

[NoRomBasic]

OK, I was able to force a hard reset (for anyone else trapped here this is done, BTW using this procedure):

1. Turn your Lumia 1520 off. (in this case I had to wait until the phone turned itself off as holding down the power button simply took me back the BSOD)
2. Press Volume DOWN and keep pressing it while you connect the charger until you see an exclamation mark!.
3. Press - in this order - Volume UP - Volume DOWN - POWER - VOLUME DOWN.
4. Your phone will reset and reboot. Could take a LONG Time

Like you treetownal it got me back to the "gears" screen. but it does seem to be moving along faster than what you were seeing.

Again, I'll update as I see more.

- Michael

 

[NoRomBasic]

OK, I'm back in. Phone is now on the "Welcome to Windows Phone" screen...

 

[liam-ward]

OK, I was able to force a hard reset (for anyone else trapped here this is done, BTW using this procedure):

1. Turn your Lumia 1520 off. (in this case I had to wait until the phone turned itself off as holding down the power button simply took me back the BSOD)
2. Press Volume DOWN and keep pressing it while you connect the charger until you see an exclamation mark!.
3. Press - in this order - Volume UP - Volume DOWN - POWER - VOLUME DOWN.
4. Your phone will reset and reboot. Could take a LONG Time

Like you treetownal it got me back to the "gears" screen. but it does seem to be moving along faster than what you were seeing.

Again, I'll update as I see more.

- Michael

I'm glad you lot are getting this sorted. If it was me i would be crying by now.

 

[NoRomBasic]

I'm glad you lot are getting this sorted. If it was me i would be crying by now.

It helps a bit to have been an MS Beta Tester since Windows XP. :sweaty: If I had a nickel for every time I installed a Beta/RC over a "dirty" O/S and ended up staring at a BSOD I'd be fairly well off these days.

Hopefully by posting what worked from a recovery standpoint will help others as I'm seeing enough tweets and posts out there to believe that a small but significant number of experimenters are running into some real issues.

- Michael

 

[Will6371]

Holy s!it sticks batman.

I knew I should have waited to download it.

 

[BroJim62]

These instructions DO NOT ... I repeat ... DO NOT work! :unhappy:

Any other ideas?

Thanks...

 

[myrandex]

Fyi everyone I was able to get around this on my own. I had considered just letting the battery drain, but I went ahead and attempted the power button and volume down button reboot trick and that successfully reset the phone. Then I was greeted by the familiar gears of the phone reflashing itself to stock settings. I did inform Microsoft of this issue too so hopefully it is identified and repaired prior to public release.

Jason

 

[adrian1338]

It helps a bit to have been an MS Beta Tester since Windows XP. :sweaty: If I had a nickel for every time I installed a Beta/RC over a "dirty" O/S and ended up staring at a BSOD I'd be fairly well off these days.

Hopefully by posting what worked from a recovery standpoint will help others as I'm seeing enough tweets and posts out there to believe that a small but significant number of experimenters are running into some real issues.

- Michael

so you have been a beta tester for Microsoft since XP and you don't get the idea to hard reset your phone when you expect it to be bricked? how would you even be able to say bricked when you didn't even try a hardreset :O

 

[Ashwini Shetty]

Hey.. This works and i was able to restart my phone when it was bricked. Thank you so much

 

[NoRomBasic]

so you have been a beta tester for Microsoft since XP and you don't get the idea to hard reset your phone when you expect it to be bricked? how would you even be able to say bricked when you didn't even try a hardreset :O

Well, in the immortal words of Ray Croc, "If You are Green, You Are Growing". I have never believed that I have the answers to everything and one of the big reasons that I enjoy being in forums such as this is that everyone at every level of the learning curve has something to contribute and it may be something I've not learned yet. So I personally always try to stay "green".

"Bricked" might not technically be the correct term since ultimately the phone was able to the be reinitialized (and I actually did not create the subject line for this thread). But from an O/S standpoint it certainly was in what I would term an "unrecoverable error": that was only reparable by (to use a PC analogy) reformatting and reinstalling the O/S. Of course I get the idea of attempting a "Hard Reset" and I've even flashed a phone or two in my time, but in this case having not run into a boot failure at this level before I hadn't learned Nokia's special (and fairly complex) key combination to get it to reinitialize. Hence rather than giving up in tears and returning the phone to Nokia I reached out to my network, learned something new (to me at least) and shared it with the group, many of whom also when confronted with a device that cannot be booted and cannot be shut down would likely use the term "Bricked" as well. So hopefully if someone is looking for answers they might find a way out of what is seemingly an unrecoverable situation.

And to be perfectly fair to MS, I stopped beta testing with them right after Vista. They changed how they do Betas with the Vista program and for me I no longer felt that feedback from their enthusiasts group was getting enough priority to justify the hours of effort it took to really beat up on an O/S and flush out true usability issues. But that would be a thread for another day. :wink:

- Michael

 

[myrandex]

Yea I shouldn't have used the word bricked. I did start reporting this prior to attempting to reboot the phone or anything, and later added the information.

 

[MDMcAtee]

So the button push instructions,are you holding down say the power button or just pushing them in that sequence independently?

Thanks

Mac

Sent from my RM-940_nam_att_200 using Tapatalk