Discontinuation bricking: Difference between revisions
Tone warning for lack of professionalism |
→Dependence on third-party bypasses: delinkification |
||
| Line 30: | Line 30: | ||
===Dependence on third-party bypasses=== | ===Dependence on third-party bypasses=== | ||
After a product has been bricked, a consumer may wish to repair their product and return it back to a functioning state. De-bricking a product is not impossible but can be difficult depending on the severity of the problem. Consumers will inevitably look to third-parties for methods to bypass the bricking which may open the user to [[security]] and | After a product has been bricked, a consumer may wish to repair their product and return it back to a functioning state. De-bricking a product is not impossible but can be difficult depending on the severity of the problem. Consumers will inevitably look to third-parties for methods to bypass the bricking which may open the user to [[security]] and safety risks. Bypasses may end up being expensive, with more complicated server-dependent products needing potentially complicated server infrastructure. | ||
===Resale falsification=== | ===Resale falsification=== | ||