Hacker News new | ask | show | jobs
by byjove 4586 days ago
Browse the support forums of carries and device makers and you'll find plenty of such testimonials. They would brick their devices and find themselves without warranty, which is not exactly an ideal situation.
1 comments

It's not unheard of, but extremely rare to "brick" modern phones. Four years ago, when you had to replace the bootloader you could flash something that would "brick" a device to the point that only JTAG could fix it, but that hasn't been typical since the Nexus One. More commonly you can still access fastboot or ODIN and restore a system image which returns the device to a stock OS. This isn't ideal for non-tech savvy users, but it is a recoverable state.
I recovered once that way, but it is definitely an unrecoverably bricked device for my parents and even for my brother.

An app that bricks even <1% of the devices just doesn't belong in the app store where it gets exposure to lots of non technical users.

Why doesn't CyanogenMod replace or repair bricked devices, when their software caused that problem in the first place?

Why should Google or the device manufacturer pay for it?

Because it comes without any implied warranty as per the Apache 2.0 license[1] they use. Though when they go and put it on the Android Market, that creates a gray area that was not an issue when it was confined to the Android Modding Forums.

Users installing it outside the market though as it was always installed have no more right to Cyanogen giving them a new device than Debian or the Linux Foundation would if you destroy your PC installing Debian Linux.

https://github.com/CyanogenMod/android_packages_apps_CMAccou...