3 ms·

There's plenty of opportunity. For example, there are reports of flashing the wrong firmware (Galaxy Note) on a similar phone (Galaxy SIII) can lead to bricking

by cfstras 10y ago

There's plenty of opportunity. For example, there are reports of flashing the wrong firmware (Galaxy Note) on a similar phone (Galaxy SIII) can lead to bricking touchscreen controller-

darklajid 10y ago
There's also plenty of opportunity to accidentally drop your phone in the loo. Common sense and being somewhat careful helps in the vast majority of things, flashing your phone included. That said, even if you flash stuff without reading instructions or fully understanding what you do: Most errors I've seen are flat-out not working (software stating: "Can't do this, you're messing up") or recoverable/soft-bricks only. (In the end it doesn't matter if you CAN kill your phone by flashing nonsense: That still wouldn't make a good argument for "Flashing voids the manufacturer's warranty". I'd just mean that those individuals who bricked their phone .. might not be covered.)
- SixSigma 10y ago
  Since when is dropping your phone in the toilet covered under warranty ? Apple added "been in water detection" to avoid payout on that very activity.
  - singold 10y ago
    The thing is that if you drop the phone in the toilet you aren't covered but that doesn't mean that you void your guarantee by using your phone while you are there, for me that's the difference. If I flash my phone and later some part of it breaks because it came bad from factory, that is independent of me flashing the phone and should be covered.
  - 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 ago
      It'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 ago
        Are you aware if eMMC firmware is signed?

by cfstras 10y ago

There's plenty of opportunity. For example, there are reports of flashing the wrong firmware (Galaxy Note) on a similar phone (Galaxy SIII) can lead to bricking touchscreen controller-

darklajid 10y ago

There's also plenty of opportunity to accidentally drop your phone in the loo. Common sense and being somewhat careful helps in the vast majority of things, flashing your phone included. That said, even if you flash stuff without reading instructions or fully understanding what you do: Most errors I've seen are flat-out not working (software stating: "Can't do this, you're messing up") or recoverable/soft-bricks only. (In the end it doesn't matter if you CAN kill your phone by flashing nonsense: That still wouldn't make a good argument for "Flashing voids the manufacturer's warranty". I'd just mean that those individuals who bricked their phone .. might not be covered.)

SixSigma 10y ago
Since when is dropping your phone in the toilet covered under warranty ? Apple added "been in water detection" to avoid payout on that very activity.
- singold 10y ago
  The thing is that if you drop the phone in the toilet you aren't covered but that doesn't mean that you void your guarantee by using your phone while you are there, for me that's the difference. If I flash my phone and later some part of it breaks because it came bad from factory, that is independent of me flashing the phone and should be covered.
- 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 ago
    It'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 ago
      Are you aware if eMMC firmware is signed?