And, speaking of the Win 10 Mobile Beta Test program ..... here is the next "unknowing, unwilling" installation bricking kerfuffle.
http://www.windowscentral.com/non-supported-phones-will-see-windows-10-mobile...Windows 10 MobileAlong with the list of officially supported handsets, it looks like several non-Lumia phones were also able to download and install Windows 10 Mobile build 10536.
That's due to a "detectoid" bug, according to Gabe Aul, who has stated that the build will not work on a non-supported device, and that installing it will require a reflash to get the phone back to a functioning state.
Once again folks, if you see Windows 10 Mobile build 10536 on non-Lumia devices, do not download and install it. You'll just end up having to reflash your device.
Here's the official list of phones supported by the Windows Insider program:
Lumia 430
Lumia 435
Lumia 520
Lumia 521
Lumia 525
Lumia 526
Lumia 530
Lumia 532
Lumia 535
Lumia 540
Lumia 620
Lumia 625
Lumia 630
Lumia 635
Lumia 636
Lumia 638
Lumia 640
Lumia 640 XL
Lumia 720
Lumia 730
Lumia 735
Lumia 810
Lumia 820
Lumia 822
Lumia 830
Lumia 920
Lumia 925
Lumia 928
Lumia 930
Lumia 1020
Lumia 1320
Lumia 1520
Lumia Icon
HTC One (M8) for Windows
**Update:* We've heard back from users stating that the update has been downloaded automatically to those running Windows 10 Mobile on unsupported devices, even with automatic updates turned off. If you're running the preview on non-sanctioned devices, we advise you de-list from the Insider Program until the issue is resolved.
Source: Twitter (Gabe Aul); Via: WinBetaOuch ..... more bricked dead "other brand" phones, huh? And, although MS pushed the update out to all the Beta Testers and MS triggered the update automatically and it was MS's bad update that bricked the hardware,
but this time MS says they have no responsibility to you financially because they done told you all you off-branders REPEATEDLY to DE-LIST from the Beta program because unless you own one of a
very select few MS built phones that the stuff actually works on it jest isn't safe for you to touch?
Sorta like saying your mobile pusher engine is totally out of control and can't tell what sort of phone the user has so they all get the same potentially harmful package no matter WHO they are ..... that's like saying your pusher engine is crap, you know.
Oh, bad buggy detectoids again -- I see.
Right. What will the EU Fair Trade Commission have to say about that, I wonder ...... you know, the free Win 10 mobile that everyone was promised that would run on all Windows phones
and in fact is only running on MS own Lumina brand phones and
is actually killing off all the other brand phones automatically, I mean.
Is that possibly considered "In restraint of free trade"? Or is it just plain old "negligent property damage" instead?
..... mebbe if they can tell whose detectoid it was that had the death dealing bug in it then perhaps they can assign all the damages $$$ to that detectoid's owner.
The owner of the malicious detectoid is after all, the one responsible, according to MS.
Hey, that's YOU, MS -- it is
all on you.
Doing such stuff twice means that the second instance is fully actionable for all harm done the second time around, since you KNEW it would kill those non-Lumina phones
and you dispersed the upgrade anyway through a non-discerning, known to be broken pusher engine.
"Trust us" ----- right.