Build 10136 Update Bug - Please Explain

SangNaga

New member
Dec 19, 2012
5
0
0
Have they ever elaborated more about this bug other than a bug when upgrading from 10080?

In other words:

Does this affect all phones? All carriers?

\What is the bug? Does is brick your phone? Does it crash requiring a Recovery Tool roll back?

How frequent is the bug? Is it guaranteed every time, or is it a 50% chance?

If we have to roll back to 8.1 to have a guaranteed successful upgrade to 10136, can we just give it a try and if it works great, or is moving from 10080 a lost cause?

Any thoughts and sources?
 
There is nothing to exaggerate. If you want 10136, you need to roll back to 8.1 first.

You CANNOT upgrade to 10136 from 10080.
 
wp_ss_20150615_0001.jpg
i want to know which is this build?
and should i have to recover it 8.1 for the installation of latest build 10136!!!
 
I would not roll back to 8.1 until 10136 build actually gets pushed tomorrow. Who knows, MS could accidently fix 10080 build update bug by then!

Doubt bug would get fixed by then,tomorrow 10136 comes out as gabe has prepped the update to launch then,he said if they were to fix the bug it would take another week but everyone said they want it now.
 
@taymur, rolling back was quite easy and painless. Reinstalling all your programs and start screen can take a while afterwards, but you could probably skip that part since you will have to do it after the update again.
 
how many rolled back successfully without bricking their phone?
Rollback is pretty quick once you have the proper file downloaded, does not take a minute. Make sure you select a proper backup to restore. I managed to select the one done by 8.1 GDR2 and I got a blue : ( screen. I had to flash the phone again and set up from scratch. Also if the phone is hot, wait before it cools down before continuing, it happened to me that it failed to restart and it gave me a scare.
 

Members online

No members online now.

Forum statistics

Threads
339,465
Messages
2,262,487
Members
428,759
Latest member
jekkylords