4 ms·
I never claimed that this was under warranty. I'm constantly trying to use this thread to kill any connection between 'rooted my phone', 'flashed a different fi
by darklajid 10y ago
I never claimed that this was under warranty. I'm constantly trying to use this thread to kill any connection between 'rooted my phone', 'flashed a different firmware' and 'bricked my phone'.
GP replied to one of my posts, saying that there IS a real risk of bricking your phone when you flash it (I don't disagree, but consider it unlikely).
By comparing the process with a totally different ~real risk~ (phone -> toilet) I'm trying to drive the point home that it isn't a problem of either flashing your phone or playing some mobile game on that white throne of yours, it is a problem of being careless. Bricking my phone shouldn't be covered by a warranty. Flash or flush doesn't matter.
But trying to imply that the warranty is void because I installed software is overly broad and crazy: If I flash CM today and the phone dies in a month from now due (battery dead, hardware issues w/ screen or power button, antenna issues, pick anything faulty you had with a vanilla/unchanged handset in the past), then CM isn't to blame and my phone has a working warranty (for all I know, for all I care - and anything else seems completely unacceptable in my world).
- ce4 10y agoIt's possible, but rare. As an example, some Samsungs had faulty eMMC chips (used in the Galaxy Nexus, SGS2 and Note 1) and certain operations when installing custom ROMs (eMMC secure erase/wipe) would trigger the infamous BrickBug that crashes the eMMC chip from next boot on. The problem was faulty eMMC firmware that Samsung later patched but never acknowledged (it was discovered by reverse engineering [1]) and worked around. [1] https://plus.google.com/+AndrewDodd/posts/Drq9uJbkGfq https://plus.google.com/+AndrewDodd/posts/Drq9uJbkGfq
- tmzt 10y agoAre you aware if eMMC firmware is signed?