No matter how messed up a desktop is, you can always format it and reinstall of a live boot. Why can't you do the same thing with a droid?

  • 9
    You could brick a computer if you wiped out or corrupted the BIOS to the point that you'd most likely have to manually reprogram the chip with a special connector. With direct regards to your question, though, this seems like kind of an apples and oranges comparison. Computers support multiple boot mediums (USB, optical disc, hard drive, etc) whereas a phone/tablet simply isn't designed that way. Some can be reflashed with desktop utilities like Odin, but where are you going to get a live version of Android (for ARM, not x86) and how are you going to boot it on a phone? – eldarerathis Oct 16 '12 at 15:57
  • 3
    @eldarerathis That sounds like it should be posted as an answer ;) – Matthew Read Oct 16 '12 at 21:31

The risk of really "bricking" a phone is not that high as it may seem, at least with more recent models, as there are multiple levels of safety-guards in place: If you break your regular system, there's a fallback possible to the recovery mode. If that's broken as well, there are things like Fastboot in place. Only if you break the lowest level, and e.g. flash an incompatible radio image (the radio image is the layer bridging the hardware to a software layer, to simplify the explanation -- see also Al's comparision with the PC's BIOS in his comment to your question: if the BIOS is broken, you no longer can start your computer), your device is really "bricked".

To understand the difference, you should also see what is different between installing your "desktop OS" on a computer and flashing your Android device: Installing your desktop OS works on a file level. That is, you boot from e.g. a DVD, and then copy files to your harddisk. On Android, flashing a ROM means to copy the entire file system at once. And you cannot boot a live system from DVD or the like -- especially when newer devices like the Nexus 4 come without even a sdcard slot.

  • 2
    I'd just like to emphasize that the risk of "bricking" is still relatively high, mainly due to the ease of running powerful software such as adb and fastboot. A single mistyped fastboot command may be sufficient to prevent the device from connecting via USB, therefore preventing it from being fixed. – anol Dec 14 '13 at 17:55

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.