Nokia Cyan update is bricking some users' phones
If you can't wait for a solution, Microsoft does have an idea. The software giant suggests that those with the developer preview, downgrade to commercial software first, before downloading Nokia Cyan. If it's too late and your phone has been bricked after an attempt to install the new OS build, you will need to use the Nokia Recovery Software Tool to "un-brick" your handset.
Keep in mind that it is only those with the Windows Phone 8.1 Preview for Developers using BitLocker, that are having the problem. If you're running Windows Phone 8 on your handset, waiting for Nokia Cyan to arrive just like any ordinary Joe, you shouldn't have a problem at all. This must be the Mobile God's idea of payback against those who were able to use the developer preview of Windows Phone 8.1 to brag about receiving Cortana before the update rolled out to others.
8. ScottSchneider (Posts: 316; Member since: 06 Dec 2011)
Well... I though "Nokia" is the Brick and not some update makes it a Brick... :)
9. RaKithAPeiRiZ (Posts: 1334; Member since: 29 Dec 2011)
Even Nokia's updates live up to the term "Made like a brick" lol
15. NokiaFTW (Posts: 1976; Member since: 24 Oct 2012)
A ''brick'' that is still more usable than your brains.
20. Arte-8800 (limited) (Posts: 4281; Member since: 13 Mar 2014)
Nokiawp devices looks likea brick.
13. NokiaFTW (Posts: 1976; Member since: 24 Oct 2012)
Stupid kid trying to act mature pops up again. Don't you have any homework or projects to do kid?
17. microsoftnokiawin (Posts: 962; Member since: 30 Mar 2012)
QUOTE "A ''brick'' that is still more usable than your brains. "
who's the kid now stop acting like a grown up you're biased and closed minded
18. Arte-8800 (limited) (Posts: 4281; Member since: 13 Mar 2014)
He surely is the immature kid.
Immature fanboy kid. A Nokiawp fanboy.
30. PhoneArenaUser (Posts: 5478; Member since: 05 Aug 2011)
You don't have a strength to admit that there is a problem with Nokia Cyan update. Instead of admitting the problem you desperately trying to insult other. Pathetic...
16. microsoftnokiawin (Posts: 962; Member since: 30 Mar 2012)
funny how microsoft hasn't been in charge for 2 month and they've already screwed something up !!
but to be fair nokia scerwed those up a few times as well just not on this level !
2. 0xFFFF (Posts: 2951; Member since: 16 Apr 2014)
Now I believe that Windows for Phone really is based on Windows for PC.
7. sriuslywtf (Posts: 221; Member since: 09 Jul 2013)
So, theres a possibility that we will see the infamous BSOD on WinPhone?
11. WahyuWisnu (Posts: 1001; Member since: 29 May 2014)
This time, they color it redish pink!! as in brick
12. WahyuWisnu (Posts: 1001; Member since: 29 May 2014)
What you should expect from MS is, NEXT VERSION WILL FIX IT... or maybe the next one... or maybe the next one... or maybe the next one... or maybe the next one... or maybe the next one... or maybe the next one... or maybe the next one...
24. elitewolverine (Posts: 1516; Member since: 28 Oct 2013)
That is how i feel about android. 4 updates in two months to fix bricking calls and sms for the note 3, s5's.
29. AfterShock (Posts: 2798; Member since: 02 Nov 2012)
Blame Sammy, not android,I don't have them issues at all.
Nice blanket cover statement though.
34. NOLATechy (Posts: 16; Member since: 08 Nov 2013)
Oh, so when Windows Phone has a problem with firmware code written by Nokia BEFORE Microsoft took over, it's Microsoft's fault, but when Android has a problem with firmware code written by Samsung, it's Samsung's fault. Way to pick and choose there!
4. Penny (Posts: 1135; Member since: 04 Feb 2011)
To clarify a bit further, Microsoft is only suggesting that users who have already bricked their phones use the available software to revert their phone back to 8.0. Everybody else on Dev Preview currently is safe.
Also, this is only affecting a small subset of WP8.1 users -- those with BitLocker encryption on their device. This feature is only available to corporate users, so general consumers remain unaffected. However, Microsoft has gone ahead and halted the Cyan update to all 8.1 Dev Preview users until a fix for the BitLocker issue is released. So even if you don't have BitLocker, just sit tight and wait for the fix to be released, after which Microsoft will resume the Cyan rollout.
5. hamster_99 (Posts: 2; Member since: 06 May 2014)
well Atleast theyve offerred the solution for the problem as well... happy about that...
6. leewt (Posts: 6; Member since: 02 May 2014)
I can't believe that this happened from Microsoft and Nokia thanks for the God that I didn't use preview for developers :)
10. tigermcm (Posts: 709; Member since: 02 Sep 2009)
its not that serious there is and has been a revory tool for Nokia
23. o7o (Posts: 56; Member since: 26 Jun 2009)
Actually even if you did, you wouldn't have faced this problem, cuz probably you weren't using BitLocker, were you?
21. Arte-8800 (limited) (Posts: 4281; Member since: 13 Mar 2014)
Bugs and viruses
An advice, do not update, until Wp8.2
27. WahyuWisnu (Posts: 1001; Member since: 29 May 2014)
WP 8.2 will fix WP 8.1
WP 8.3 will fix WP 8.2
The microsoft next version will fix it song...
28. elitewolverine (Posts: 1516; Member since: 28 Oct 2013)
And android will do the same over and over.
Know how many updates our s5's and note 3's have had in just a very few short months to fix sms issues?
If you think any software is free of bugs, i have a bridge to sell you, actually a Note 3 to sell ya (be carefull its my 3rd one).
32. Doakie (Posts: 1224; Member since: 06 May 2009)
Still haven't seen this update on my T-Mobile 521.... I'm hitting "Phone Update" hourly just hoping I finally get a chance to play with 8.1...... Getting frustrated. /whine /whine /whine.....
33. roscuthiii (Posts: 1788; Member since: 18 Jul 2010)
Cyan? BSoD? It's kismet. This update was destined to kill a MS phone.
35. NOLATechy (Posts: 16; Member since: 08 Nov 2013)
Haters will be haters. It seems like the Apple and Android fannies love to troll the sites on issues like this to promote how much better their products are than Microsoft. All the while forgetting the many, many update problems BOTH Apple and Android have had (lest we forget Antenna-gate for iPhone and Reboot issues on Android JellyBean). No phone is perfect people, but I at least applaud Microsoft for admitting the problem and halting the update. I'm sure they will have this fixed very quickly.